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.

Sovereigndwp/bitcoin-sovereign-academy

https://github.com/Sovereigndwp/bitcoin-sovereign-academy · scanned 2026-06-16 00:19 UTC (2 months, 2 weeks ago)

530 raw signals (0 security + 530 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 516 actionable findings from 1 signal source. 14 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 · 516 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 39 Medium 339 Low 123 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 516 Crowd 0 Layer: Frontend 91 Security 307 Cicd 5 Quality 60 Api 53

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.

Legacy markers 3 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.

3 matching findings on this repo

low Old/deprecated-named symbol `includeLegacy` in js/progress-manager.js:654
low Old/deprecated-named symbol `hdLegacy` in interactive-demos/bitcoin-key-generat…
low Old/deprecated-named symbol `generateFakeLegacy` in interactive-demos/address-f…

View all legacy markers findings →

Commented-out code 9 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/`.

9 matching findings on this repo

info Commented-code block (7 lines) in deep-dives/bitcoin-capital/_drafts/loans-math…
info Commented-code block (8 lines) in api/tutor.ts:23
info Commented-code block (6 lines) in js/module-gate.js:15
info Commented-code block (5 lines) in js/reflect-widget.js:36
info Commented-code block (5 lines) in js/kpi-tracking.js:318
info Commented-code block (6 lines) in js/analytics.js:458
info Commented-code block (5 lines) in scripts/nostr/zap-profile-check.mjs:4
info Commented-code block (5 lines) in interactive-demos/bitcoin-key-generator-visua…
info Commented-code block (5 lines) in programa-colombia/program-state.js:300

View all commented-out code findings →

Config drift 4 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.

4 matching findings on this repo

low Stray `console.log` in TS/JS — js/config.js:108
low Stray `console.log` in TS/JS — tools/domain-config.js:53
medium Insecure pattern 'node_child_process' in tools/domain-config.js:10 tools/domain-config.js:10
medium Runtime service client appears to use placeholder configuration

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/398d0142-65d7-4c39-8041-f031443865a9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/398d0142-65d7-4c39-8041-f031443865a9/

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.