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.
Sign up free Scan another repo
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)

File as issue Image
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
Combined
58.5
/100
Security checks
69
85 findings
System graph
48
100.0% cov · 165 findings
Critical
8
click to filter
Agents
10
0 votes
Crowd
0
reported
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
Severity: Critical 8 High 42 Medium 64 Low 77 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 85 System graph 165 Crowd 0 Layer: Cicd 13 Software 35 Quality 93 Security 91 Frontend 3 Network 10 Hardware 5

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in aider/analytics.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in aider/analytics.py:56; move to env var / secrets manager.
aider/analytics.py:56
#2
subprocess shell true — aider/commands.py:980
GapSeverity.CRITICAL Layer.SECURITY score 0.500
Why: critical severity
#3
subprocess shell true — aider/editor.py:134
GapSeverity.CRITICAL Layer.SECURITY score 0.500
Why: critical severity
#4
subprocess shell true — aider/io.py:1094
GapSeverity.CRITICAL Layer.SECURITY score 0.500
Why: critical severity
#5
subprocess shell true — aider/run_cmd.py:67
GapSeverity.CRITICAL Layer.SECURITY score 0.500
Why: critical severity
#6
CVE-2026-35030: litellm 1.82.3 — requirements.txt
GapSeverity.CRITICAL Layer.SECURITY score 0.500
Why: critical severity
#7
CVE-2026-42208: litellm 1.82.3 — requirements.txt
GapSeverity.CRITICAL Layer.SECURITY score 0.500
Why: critical severity
#8
CVE-2026-49468: litellm 1.82.3 — requirements.txt
GapSeverity.CRITICAL Layer.SECURITY score 0.500
Why: critical severity
#9
Insecure pattern 'python_os_system' in benchmark/README.md:26
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmark/README.md:26
#10
Insecure pattern 'subprocess_shell_true' in aider/commands.py:974
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
aider/commands.py:974

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.