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.

tubby124/unmissed-ai

https://github.com/tubby124/unmissed-ai · scanned 2026-06-16 00:43 UTC (2 months, 1 week ago)

549 raw signals (0 security + 549 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 548 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 115 Low 263 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 548 Crowd 0 Layer: Api 1 Frontend 340 Network 2 Security 17 Cicd 2 Quality 186

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 `isLegacy` in scripts/drift-check-all.ts:90
low Old/deprecated-named symbol `hasLegacy` in scripts/p3-fleet-snapshot-audit.ts:47
low Old/deprecated-named symbol `_buildPrompt_legacy` in src/lib/prompt-builder.ts:5

View all legacy markers findings →

Commented-out code 77 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 cloudflare-workers/voice-fallback/src/index.t…
info Commented-code block (7 lines) in tests/phase4-settings-e2e.spec.ts:52
info Commented-code block (5 lines) in tests/v2-modal-shiptest.spec.ts:436
info Commented-code block (5 lines) in tests/smoke-trial-flow.spec.ts:159
info Commented-code block (6 lines) in tests/schemathesis/conftest.py:222
info Commented-code block (7 lines) in tests/truth-audit/tenant-isolation.spec.ts:90
info Commented-code block (5 lines) in tests/truth-audit/transfer-recovery.spec.ts:71
info Commented-code block (8 lines) in tests/promptfoo/knowledge-routing/audit.ts:269
info Commented-code block (5 lines) in tests/promptfoo/scripts/generate-auto-glass-p…
info Commented-code block (6 lines) in scripts/deploy_prompt.py:44
info Commented-code block (6 lines) in scripts/migrate-velly-to-slots.ts:75
info Commented-code block (6 lines) in scripts/register-ultravox-webhook.py:78

View all commented-out code findings →

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

6 matching findings on this repo

info `truncate` class without `title=` for hover reveal — src/components/dashboard/A…
low Stray `console.log` in TS/JS — src/app/api/admin/configure-sms-webhooks/route.t…
low Stray `console.log` in TS/JS — src/app/api/admin/backfill-niche-configs/route.t…
low Very large file: src/lib/prompt-config/niche-defaults.ts (1564 lines)
medium `fetch()` without try/.catch or AbortSignal — src/app/api/admin/configure-sms-w…
info Commented-code block (5 lines) in src/lib/prompt-config/niche-defaults.ts:785

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/a1e69c83-e2b3-492e-bbaa-30c5463f53c9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a1e69c83-e2b3-492e-bbaa-30c5463f53c9/

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.