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.

Silex-Research/DontPanic

https://github.com/Silex-Research/DontPanic · scanned 2026-06-16 00:13 UTC (2 months, 2 weeks ago)

351 raw signals (0 security + 351 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 334 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

88.9% cov · 334 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 9 Medium 39 Low 86 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 334 Crowd 0 Layer: Software 10 Frontend 3 Network 1 Security 26 Quality 294

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 3 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 9 places

View all duplicates & near-duplicates findings →

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

10 matching findings on this repo

low Old/deprecated-named symbol `project_legacy` in scripts/dontpanic_orchestrate/r…
low Old/deprecated-named symbol `global_legacy` in scripts/dontpanic_orchestrate/te…
low Old/deprecated-named symbol `test_default_prefers_existing_dontpanic_dir_over_l…
low Old/deprecated-named symbol `hr_env_legacy` in scripts/dontpanic_orchestrate/te…
info Commented-code block (6 lines) in scripts/dontpanic_orchestrate/tests/test_lega…
low Old/deprecated-named symbol `projectF001ToLegacy` in dashboard/config-firebase.…
low Old/deprecated-named symbol `projectF001ToLegacy` in dashboard/tests/integratio…
low Old/deprecated-named symbol `fixtureLegacy` in dashboard/tests/unit/architectur…
info Commented-code block (5 lines) in dashboard/tests/unit/legacy-theme-bridge-f002…
low Old/deprecated-named symbol `projectF001ToLegacy` in dashboard/tests/unit/confi…

View all legacy markers findings →

Commented-out code 193 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 docs/design/dashboard-platform-roadmap-v1/cla…
info Commented-code block (5 lines) in docs/plans/2026-05-06-003-fix-live-cross-vend…
info Commented-code block (5 lines) in docs/plans/2026-05-07-002-fix-cross-vendor-do…
info Commented-code block (5 lines) in docs/plans/2026-05-23-005-feat-dashboard-proj…
info Commented-code block (6 lines) in scripts/quota_check.py:489
info Commented-code block (6 lines) in scripts/dontpanic_doctor.py:843
info Commented-code block (6 lines) in scripts/sanitization_check.py:29
info Commented-code block (5 lines) in scripts/dontpanic_orchestrate/command_validat…
info Commented-code block (5 lines) in scripts/dontpanic_orchestrate/quota_admission…
info Commented-code block (5 lines) in scripts/dontpanic_orchestrate/plan_loader.py:…
info Commented-code block (6 lines) in scripts/dontpanic_orchestrate/operator_consol…
info Commented-code block (12 lines) in scripts/dontpanic_orchestrate/quota_caps_loa…

View all commented-out code findings →

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

12 matching findings on this repo

low Very large file: scripts/dontpanic_orchestrate/config_inventory.py (2280 lines)
low Very large file: scripts/dontpanic_orchestrate/tests/test_config_inventory_f008…
info Commented-code block (5 lines) in scripts/dontpanic_orchestrate/config_inventor…
info Commented-code block (5 lines) in scripts/dontpanic_orchestrate/project_config.…
low Old/deprecated-named symbol `test_default_prefers_existing_dontpanic_dir_over_l…
low Old/deprecated-named symbol `test_corrupt_registry_refuses_create_before_any_co…
info Commented-code block (6 lines) in scripts/dontpanic_orchestrate/tests/test_f003…
info Commented-code block (6 lines) in scripts/dontpanic_orchestrate/tests/test_conf…
info Commented-code block (5 lines) in scripts/dontpanic_orchestrate/showcase/config…
medium `fetch()` without try/.catch or AbortSignal — dashboard/playwright.config.js:17
low Old/deprecated-named symbol `projectF001ToLegacy` in dashboard/config-firebase.…
info Commented-code block (5 lines) in dashboard/config-firebase.js:3

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/88941632-b7ec-4a9a-a7c0-805ab4be6be6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/88941632-b7ec-4a9a-a7c0-805ab4be6be6/

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.