JSONbored/awesome-claude

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.

20 of your 100 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.04s · analysis 50.89s · 17.7 MB · GitHub preflight 676ms

https://github.com/JSONbored/awesome-claude · scanned 2026-06-05 19:20 UTC (4 days, 16 hours ago) · 10 languages

312 raw signals (92 security + 220 graph) 40th percentile · Typescript · medium (20-100K LoC) System graph score 84 (lower by 18)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 155 actionable findings from 2 signal sources. 47 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 · 110 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	50.3	0.25	12.57
`testing_score`	77.0	0.20	15.40
`documentation_score`	87.8	0.15	13.17
`practices_score`	78.0	0.15	11.70
`code_quality`	50.8	0.10	5.08
Overall		1.00	66.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 3 Medium 22 Low 73 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 45 System graph 110 Crowd 0 Layer: Quality 44 Security 7 Software 70 Cicd 4 Api 1 Frontend 29

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 8 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/`.

8 matching findings on this repo

info Commented-code block (5 lines) in tests/mcp-submission-duplicate-urls.test.ts:1…
info Commented-code block (6 lines) in tests/helpers/zip-fixtures.ts:3
info Commented-code block (6 lines) in apps/web/vite.config.ts:1
info Commented-code block (8 lines) in apps/web/src/lib/config.server.ts:10
info Commented-code block (7 lines) in apps/web/src/lib/api/example.functions.ts:6
info Commented-code block (6 lines) in apps/web/src/lib/api/contracts.ts:394
info Commented-code block (6 lines) in packages/mcp/src/submissions.js:782
info Commented-code block (7 lines) in packages/registry/src/source-repo.js:4

View all commented-out code findings →

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

8 matching findings on this repo

low npm package `@lovable.dev/vite-tanstack-config` is minor version(s) behind (2.1… apps/web/package.json
info npm package `@commitlint/config-conventional` is patch version(s) behind (21.0.… package.json
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: integrations/raycast/eslint.config.js
low File has no detected symbols: tests/mcp-config-validator.test.ts
low File has no detected symbols: apps/web/eslint.config.js
info Commented-code block (6 lines) in apps/web/vite.config.ts:1
info Commented-code block (8 lines) in apps/web/src/lib/config.server.ts:10

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/6c042ca0-07c6-4666-93ca-e40bdbbf65ef/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6c042ca0-07c6-4666-93ca-e40bdbbf65ef/

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.