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.

thedmaj/demo-recorder

https://github.com/thedmaj/demo-recorder · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

334 raw signals (0 security + 334 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 321 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 8 Medium 79 Low 166 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 321 Crowd 0 Layer: Frontend 90 Security 63 Cicd 1 Quality 112 Api 55

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 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `framesDirLegacy` in scripts/scratch/scratch/build-…

View all legacy markers findings →

Commented-out code 60 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 (5 lines) in tests/unit/slide-contract-cascade.test.js:98
info Commented-code block (6 lines) in tests/unit/prompt-fidelity-integration.test.j…
info Commented-code block (6 lines) in tests/unit/prompt-templates.test.js:101
info Commented-code block (5 lines) in tests/unit/link-token-create-config.test.js:11
info Commented-code block (6 lines) in tests/unit/dotenv-loader.test.js:76
info Commented-code block (6 lines) in tests/unit/prompt-scope.test.js:58
info Commented-code block (6 lines) in tests/unit/build-qa.test.js:153
info Commented-code block (6 lines) in scripts/auto-gap.js:59
info Commented-code block (5 lines) in scripts/test-plaid-link-record.js:453
info Commented-code block (5 lines) in scripts/validate-narration-sync.js:188
info Commented-code block (9 lines) in scripts/check-run-sync.mjs:7
info Commented-code block (5 lines) in scripts/sync-map-utils.js:37

View all commented-out code findings →

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

7 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/skills/plaid-layer-idv-on… .claude/skills/plaid-layer-idv-onboarding/SKILL.md:287
info Commented-code block (5 lines) in tests/unit/link-token-create-config.test.js:11
info Commented-code block (6 lines) in scripts/scratch/utils/link-token-create-confi…
low Unused endpoint: GET /api/config
low Unused endpoint: POST /api/config
low Unused endpoint: GET /api/config/prompt
low Unused endpoint: POST /api/config/prompt

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/537565e1-6ccc-492b-b7ff-fce5faf0e94a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/537565e1-6ccc-492b-b7ff-fce5faf0e94a/

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.