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.

toy-crane/claude-hunt

https://github.com/toy-crane/claude-hunt · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

197 raw signals (108 security + 89 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 96 actionable findings from 2 signal sources. 283 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 · 87 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 11 Medium 60 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 87 Crowd 0 Layer: Quality 68 Security 14 Software 4 Api 1 Frontend 5 Cicd 4

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 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 next.config.mjs:18
info Commented-code block (5 lines) in widgets/project-grid/ui/prompt-line.test.tsx:…
info Commented-code block (5 lines) in widgets/header/ui/header.tsx:15
info Commented-code block (6 lines) in app/robots.ts:4
info Commented-code block (5 lines) in app/(chrome)/settings/loading.tsx:6
info Commented-code block (5 lines) in .claude/skills/skill-creator/scripts/improve_…
info Commented-code block (5 lines) in artifacts/improve-main-page/references/Termin…
info Commented-code block (6 lines) in artifacts/improve-og-image/references/project…
info Commented-code block (6 lines) in entities/project/model/constants.ts:5
info Commented-code block (5 lines) in e2e/settings-auth-redirect.spec.ts:32

View all commented-out code findings →

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

7 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/references/security-check… .claude/references/security-checklist.md:30
high Agent instruction/config may expose a secret: .claude/skills/ci-cd-and-automati… .claude/skills/ci-cd-and-automation/SKILL.md:130
high Agent instruction/config may expose a secret: .claude/skills/next-best-practice… .claude/skills/next-best-practices/route-handlers…:103
high Agent instruction/config may expose a secret: .claude/skills/next-best-practice… .claude/skills/next-best-practices/self-hosting.md:291
high Agent instruction/config may expose a secret: .claude/skills/init-project/supab… .claude/skills/init-project/supabase-setup.md:29
high Agent instruction/config may expose a secret: .claude/skills/supabase/reference… .claude/skills/supabase/references/testing.md:137
info Commented-code block (5 lines) in next.config.mjs:18

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/eab29de0-6108-4b7f-a861-87768364388d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/eab29de0-6108-4b7f-a861-87768364388d/

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.