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.

richiexuetang/ritcher-map

https://github.com/richiexuetang/ritcher-map · scanned 2026-06-15 23:51 UTC (2 months, 3 weeks ago)

201 raw signals (0 security + 201 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 197 actionable findings from 1 signal source. 4 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 · 197 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 36 Medium 123 Low 22 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 197 Crowd 0 Layer: Api 1 Frontend 9 Network 2 Hardware 12 Security 50 Cicd 3 Quality 120

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 3 places repo-level

View all duplicates & near-duplicates 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 (8 lines) in .claude/helpers/session.js:13
info Commented-code block (5 lines) in .claude/helpers/intelligence.cjs:111
info Commented-code block (7 lines) in .claude/helpers/statusline.cjs:31
info Commented-code block (5 lines) in .claude/helpers/hook-handler.cjs:115
info Commented-code block (5 lines) in .claude/helpers/statusline.js:83
info Commented-code block (6 lines) in webapp/scripts/generate-category-icons.mjs:3
info Commented-code block (5 lines) in webapp/src/app/sitemap.ts:5
info Commented-code block (7 lines) in webapp/src/app/api/admin/presign/route.ts:6
info Commented-code block (5 lines) in webapp/src/lib/iconPresets.ts:1
info Commented-code block (6 lines) in webapp/src/lib/map/crs.test.ts:10

View all commented-out code findings →

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

high Agent instruction/config may expose a secret: .claude/commands/github/issue-tra… .claude/commands/github/issue-tracker.md:68
high Agent instruction/config may expose a secret: .claude/commands/github/sync-coor… .claude/commands/github/sync-coordinator.md:78
high Agent instruction/config may expose a secret: .claude/commands/github/release-m… .claude/commands/github/release-manager.md:229
high Agent instruction/config may expose a secret: .claude/commands/github/repo-arch… .claude/commands/github/repo-architect.md:228
high Agent instruction/config may expose a secret: .claude/commands/github/pr-manage… .claude/commands/github/pr-manager.md:92
high Agent instruction/config may expose a secret: .claude/commands/hooks/post-task.… .claude/commands/hooks/post-task.md:103
high Agent instruction/config may expose a secret: .claude/commands/sparc/tutorial.md .claude/commands/sparc/tutorial.md:59
high Agent instruction/config may expose a secret: .claude/commands/sparc/code.md .claude/commands/sparc/code.md:69
high Agent instruction/config may expose a secret: .claude/commands/sparc/sparc.md .claude/commands/sparc/sparc.md:91
high Agent instruction/config may expose a secret: .claude/commands/sparc/post-deplo… .claude/commands/sparc/post-deployment-monitoring…:63
high Agent instruction/config may expose a secret: .claude/commands/sparc/refinement… .claude/commands/sparc/refinement-optimization-mo…:63
high Agent instruction/config may expose a secret: .claude/commands/sparc/docs-write… .claude/commands/sparc/docs-writer.md:60

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/297a3339-e379-40e9-abaa-27499c169404/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/297a3339-e379-40e9-abaa-27499c169404/

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.