numtide/llm-agents.nix

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.

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

Scan timing: clone 2.91s · analysis 8.94s · 3.7 MB · GitHub preflight 420ms

https://github.com/numtide/llm-agents.nix · scanned 2026-06-05 19:38 UTC (4 days, 15 hours ago) · 10 languages

250 raw signals (182 security + 68 graph) 19th percentile · Python · small (2-20K LoC) System graph score 82 (lower by 28)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 15 hours ago · v2 · 169 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

88.9% cov · 22 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	40.5	0.25	10.12
`testing_score`	0.0	0.20	0.00
`documentation_score`	90.0	0.15	13.50
`practices_score`	67.0	0.15	10.05
`code_quality`	69.7	0.10	6.97
Overall		1.00	53.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 51 Medium 90 Low 15 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 147 System graph 22 Crowd 0 Layer: Software 135 Security 6 Quality 20 Cicd 4 Api 1 Network 2 Frontend 1

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

View all duplicates & near-duplicates findings →

Commented-out code 1 finding

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

1 matching finding on this repo

info Commented-code block (5 lines) in .github/ci/check_maintainers.py:30

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/8582a95d-e4bd-4239-bbd9-99545eaf9f4b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8582a95d-e4bd-4239-bbd9-99545eaf9f4b/

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.