Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Zandolfus/aspects-of-power

https://github.com/Zandolfus/aspects-of-power · scanned 2026-06-16 01:11 UTC (2 months, 1 week ago)

111 raw signals (0 security + 111 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 94 actionable findings from 1 signal source. 17 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 94 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 16 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 94 Crowd 0 Layer: Software 8 Frontend 9 Hardware 1 Security 12 Cicd 1 Quality 55 Api 8

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

info Commented-code block (7 lines) in migration/backfill_legacy_local_augment_snaps…
low Old/deprecated-named symbol `unstable_legacy` in python/App/static/assets/index…

View all legacy markers findings →

Commented-out code 29 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in module/aspects-of-power.mjs:130
info Commented-code block (6 lines) in module/sheets/actor-sheet.mjs:83
info Commented-code block (5 lines) in module/sheets/item-sheet.mjs:240
info Commented-code block (6 lines) in module/apps/celerity-combat-tracker.mjs:12
info Commented-code block (5 lines) in module/helpers/config.mjs:126
info Commented-code block (5 lines) in module/documents/item.mjs:763
info Commented-code block (5 lines) in module/documents/token.mjs:43
info Commented-code block (6 lines) in module/documents/actor.mjs:35
info Commented-code block (7 lines) in module/canvas/target-prompt.mjs:161
info Commented-code block (6 lines) in module/canvas/aoe-region-behavior.mjs:19
info Commented-code block (6 lines) in module/systems/engagement-halts.mjs:45
info Commented-code block (5 lines) in module/systems/channel.mjs:253

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

low Very large file: module/helpers/config.mjs (1316 lines)
info Commented-code block (5 lines) in module/helpers/config.mjs:126

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/01d72f20-5bf0-42ca-ad3f-f033354ff767/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/01d72f20-5bf0-42ca-ad3f-f033354ff767/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.