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.
165 of your 228 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.42s · analysis 3.49s · 77.8 MB · GitHub API rate-limit (preflight)

Aider-AI/aider

https://github.com/Aider-AI/aider.git · scanned 2026-06-24 18:07 UTC (1 month ago) · 10 languages

433 raw signals (220 security + 213 graph) 11/13 scanners ran 11th percentile · Python · medium (20-100K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month ago · v1 · 250 actionable findings from 2 signal sources. 183 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 90.0 0.15 13.50
practices_score 89.0 0.15 13.35
code_quality 45.0 0.10 4.50
Overall 1.00 85.3
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 2 findings
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.
2 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 3 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 4 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/`.
4 matching findings on this repo
  • info Commented-code block (5 lines) in tests/basic/test_coder.py:327
  • info Commented-code block (5 lines) in tests/basic/test_repo.py:557
  • info Commented-code block (6 lines) in aider/main.py:270
  • info Commented-code block (5 lines) in aider/waiting.py:153
View all commented-out code findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • high [MINED131] pre-commit hook `https://github.com/PyCQA/isort` pinned to mutable r… .pre-commit-config.yaml:2
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/bb1efda6-8d6f-4283-bc3a-3a3821e68b71/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bb1efda6-8d6f-4283-bc3a-3a3821e68b71/

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.