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.

doc-detective/doc-detective

https://github.com/doc-detective/doc-detective · scanned 2026-06-17 01:58 UTC (1 month, 1 week ago)

154 raw signals (0 security + 154 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -21.5 (diff) · 128 actionable findings from 1 signal source. 26 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 · 128 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 20 Low 49 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 128 Crowd 0 Layer: Api 1 Frontend 37 Network 1 Security 13 Cicd 5 Quality 71

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.

Commented-out code 52 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 scripts/publish-staged-release.js:4
info Commented-code block (8 lines) in scripts/postinstall.js:11
info Commented-code block (6 lines) in src/cli.ts:86
info Commented-code block (8 lines) in src/utils.ts:275
info Commented-code block (6 lines) in src/hints/index.ts:8
info Commented-code block (7 lines) in src/hints/context.ts:3
info Commented-code block (10 lines) in src/hints/render.ts:3
info Commented-code block (7 lines) in src/hints/types.ts:3
info Commented-code block (12 lines) in src/hints/hints.ts:7
info Commented-code block (6 lines) in src/agents/runner.ts:58
info Commented-code block (6 lines) in src/agents/fetcher.ts:75
info Commented-code block (5 lines) in src/agents/spawn-helper.ts:58

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

info TODO/FIXME marker in shipping code — src/core/config.ts:366
medium Insecure pattern 'node_child_process' in src/core/config.ts:6 src/core/config.ts:6
info Commented-code block (8 lines) in src/core/config.ts:512
low Old/deprecated-named symbol `config_v2` in src/common/src/validate.ts:53

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/5400d36c-835c-47bb-a39c-8bfad116d772/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5400d36c-835c-47bb-a39c-8bfad116d772/

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.