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.

Ric-Lan/the_door

https://github.com/Ric-Lan/the_door · scanned 2026-06-15 23:51 UTC (2 months, 3 weeks ago)

49 raw signals (0 security + 49 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 47 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 15 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 47 Crowd 0 Layer: Software 8 Frontend 3 Security 10 Cicd 1 Quality 25

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

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

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 `test_resolve_not_found_when_no_id_and_no_legacy` i…
low Old/deprecated-named symbol `test_serialize_snapshot_provenance_legacy` in the_…
low Old/deprecated-named symbol `test_different_contract_version_is_legacy` in the_…

View all legacy markers findings →

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

10 matching findings on this repo

info Commented-code block (5 lines) in the_door/tests/unit/mcp/_invocation_recipes.p…
info Commented-code block (5 lines) in the_door/tests/unit/hooks/test_execution_gate…
info Commented-code block (5 lines) in the_door/tests/unit/core/test_models_package_…
info Commented-code block (7 lines) in the_door/tests/unit/core/extraction/test_edge…
info Commented-code block (8 lines) in the_door/src/the_door/mcp/tools/analyze_chang…
info Commented-code block (7 lines) in the_door/src/the_door/mcp/tools/snapshot_writ…
info Commented-code block (7 lines) in the_door/src/the_door/core/diff/diff_renderer…
info Commented-code block (8 lines) in the_door/src/the_door/core/extraction/edge_bu…
info Commented-code block (5 lines) in docs/frontend-local-version-viewer/viewer/js/…
info Commented-code block (7 lines) in .claude/hooks/c3_gate_snapshot_write.py:199

View all commented-out code 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/bfa36912-c9a6-4d81-997e-64df2944adfa/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bfa36912-c9a6-4d81-997e-64df2944adfa/

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.