superpowers

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.

5 of your 13 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.37s · analysis 0.33s · 0.9 MB · GitHub API rate-limit (preflight)

https://github.com/obra/superpowers · scanned 2026-05-24 01:21 UTC (1 week, 5 days ago) · 10 languages

19 findings (12 legacy + 7 scanner) 94th percentile · Javascript · tiny (<2K LoC) Scanner says 99 (lower by 20)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 5 days ago · v1 · 19 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	98.0	0.25	24.50
`testing_score`	90.0	0.20	18.00
`documentation_score`	87.0	0.15	13.05
`practices_score`	40.0	0.15	6.00
`code_quality`	68.4	0.10	6.84
Overall		1.00	79.6

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 1 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 12 9-layer 7 Crowd 0 Layer: Security 1 Quality 12 Api 1 Frontend 4 Cicd 1

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.

Fragile runtime 10 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

10 matching findings on this repo

medium Agent control bridge may listen on a network interface without visible auth skills/brainstorming/scripts/start-server.sh:12
low [SEC132] String concat where the language has interpolation (AI style drift): S… skills/brainstorming/scripts/server.cjs:103
low Multiple AI-agent scaffold marker files are present AGENTS.md:1
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… skills/writing-skills/render-graphs.js:78
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… skills/brainstorming/scripts/server.cjs:229
info [MINED043] Http Not Https: Hardcoded http:// (not localhost) for endpoints that… skills/brainstorming/scripts/server.cjs:342
info [MINED098] Global Scope Pollution: Attaching libraries/objects directly to the … skills/brainstorming/scripts/helper.js:65
high [SEC085] JS: child_process.exec with non-literal: child_process.exec with user-… skills/writing-skills/render-graphs.js:25
high [MINED004] Weak Crypto: MD5/SHA1/DES/RC4 used for security context (not just ch… skills/brainstorming/scripts/server.cjs:12
high [SEC128] Async function without await — fire-and-forget Promise (AI mistake): A… skills/brainstorming/scripts/server.cjs:190

View all fragile runtime findings →

Commented-out code 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (8 lines) in skills/systematic-debugging/condition-based-w…

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium No CI/CD configuration found

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/ae44555f-5cc0-4369-8639-1c7618a9077e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ae44555f-5cc0-4369-8639-1c7618a9077e/

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.