Agent Reputation & TrustClearinghouse

Aider (open-source)

Category
Coding agent
Type
Open-source terminal AI pair-programming tool (Apache-2.0) maintained by Paul Gauthier and contributors; PyPI aider-chat, GitHub Aider-AI/aider
Source
Project repository
Last reviewed
2026-10-17 (what this means)

Citation check incomplete — recheck later.

Summary

Aider is an open-source command-line tool that edits code in a local git repository using a language model chosen by the user. Eight independent studies that ran it were found (five peer-reviewed). Results depend heavily on the model and task. In most studies that compared agents, Aider completed fewer tasks than OpenHands or SWE-agent with the same model, for example 1.85-16.67% task pass rate on GitTaskBench and 11.2-20.0% of vulnerabilities patched on SEC-bench, although it had lower cost per task. Results on secure-coding benchmarks were mixed. Aider with GPT-5 had the best correct-and-secure score (35.8%) of three agents on MT-Sec and was close to the leaders on SecRepoBench (50.6% secure-pass@1), but had the lowest average correct-and-secure rate (6.7%) on SecureVibeBench. Two CVEs have been published (assigned by VulDB and VulnCheck); the related GitHub issues were open with no fix identified as of 17 October 2026. The latest release is v0.86.2 (February 2026). Informational only; not a guarantee, endorsement, or certification.

Overall score: 52 · Evidence grade: A · Independent sources: 8 performance (6 peer-reviewed), 4 other

Evidence grade describes the amount and type of evidence, not the agent's quality.

Grade note: Grade A: 8 counted sources (6 peer-reviewed), and Sifting the Noise tested v0.86.1 within the last 12 months, which meets the A rule. The evidence-quality score (80) is below the suggested A range (85-100) because the A rests on that single recent versioned test, whose date is inferred from its access dates (December 2025 to January 2026). (see methodology)

Factor breakdown

Factor breakdown
FactorWeightScoreNote
Completion rate30%40GitTaskBench (v0.84.1.dev): execution completion 5.56-20.37% and task pass rate 1.85-16.67% across GPT-4o, GPT-4.1, Claude 3.5 and DeepSeek V3, the lowest of three frameworks (SWE-agent up to 42.59%, OpenHands up to 48.15%); Aider + DeepSeek V3 had the lowest cost (under $0.003 per task). SEC-bench (v0.82.0, 80 instances): 11.2-20.0% vulnerabilities patched (SWE-agent 26.2-33.8%), proof-of-concept 1.2% (Claude 3.7 Sonnet). OmniCode (Gemini-2.5-Flash): Python bug-fixing 32.4% vs SWE-agent 38.1%, C++ 1.8% vs 8.0%, Java 19.3% vs 14.7%. SecRepoBench: pass@1 56.6-70.1% across models (OpenHands up to 79.6%). Multi-Harness RL (Qwen3-8B-based models on SWE-bench Verified): mean 2.14% solved under Aider, lowest of four harnesses (OpenHands 9.27%).
Disputes20%45CVE-2026-85674 (an untrusted repository's .aider.conf.yml can set test or lint commands that run at startup without confirmation; through v0.86.2; CVSS 3.1 7.8 per VulnCheck; GitHub issue #5254 open). CVE-2026-10175 (Architect mode: prompt injection via repository files can lead to injected code being committed; reported in 0.86.3 per VulDB; CVSS 3.1 6.3; NVD Not Scheduled; VulDB states the maintainer did not respond; issue #5058 open). No fix identified for either as of 17 October 2026. No legal or regulatory action found. No release since February 2026.
Adherence to limits25%45SecureVibeBench (v0.86.1): average correct-and-secure rate 6.7%, lowest of three agents (SWE-agent 14.3%, OpenHands 13.9%). MT-Sec (v0.82.1): Aider + GPT-5 had the highest correct-and-secure score (35.8%) of three agents, though it fell by 27.3% in some multi-turn settings. SecRepoBench: secure-pass@1 39.0-50.6%; 21% of Aider + Claude Sonnet 4.5 completions did not compile. Sifting the Noise (v0.86.1): 14.3% false-positive rate when triaging static-analysis alerts (SWE-agent 14.1-14.9%), described as more stable across policies. The two CVEs concern commands or code run without user confirmation. No independent study of out-of-scope or unrequested actions by Aider was found.
Evidence quality25%80Eight independent sources, six peer-reviewed (NeurIPS 2025, AAAI 2026, EMNLP 2026, ACL Findings 2026, ISSTA 2026, LLM4Code workshop at ICSE 2026). Stated versions are v0.82.0, v0.82.1, v0.84.1.dev and v0.86.1 (twice). Sifting the Noise tested v0.86.1; the test date is not stated, but its access dates (December 2025 to January 2026) place it within 12 months, so grade A. This score is below the methodology's suggested A range (85-100) because the A rests on a single recent versioned test whose date is inferred.

0.30 × 40 + 0.20 × 45 + 0.25 × 45 + 0.25 × 80 = 52.25, rounded to 52 (rounding rule).

Scope

The open-source Aider command-line tool (aider-chat), run with a language model chosen by the user, from v0.82.0 (April 2025) through v0.86.2 (12 February 2026) and the main branch (last commit 22 May 2026). The Aider leaderboards (Polyglot, code editing, refactoring) are run by the maintainer and are not counted. Results depend heavily on the language model and task, so they are reported as ranges by model.

Version and status note

Aider's latest release is v0.86.2 (12 February 2026); the main branch was last updated on 22 May 2026.

How sources were counted

The Aider maintainer runs the Aider leaderboards, so those results are listed but not counted. Studies with Aider developers as co-authors would be excluded; none were found. Aggregator sites that republish leaderboard figures are not counted.

Disclosures for counted sources

No counted study has Aider developers as authors. One SecRepoBench author is affiliated with Google DeepMind. MT-Sec and SecRepoBench share authors, as do SecureVibeBench and Sifting the Noise.

Security

Aider runs commands and edits files in the user's repository. CVE-2026-85674: a repository's configuration file can set test or lint commands that run without confirmation, affecting versions through v0.86.2 (CVSS 3.1 7.8, VulnCheck; GitHub issue #5254 open). CVE-2026-10175: prompt injection in Architect mode can lead to injected code being committed (CVSS 3.1 6.3, VulDB; NVD status: Not Scheduled; VulDB states the maintainer did not respond; GitHub issue #5058 open). No fix was identified for either as of 17 October 2026. No legal or regulatory action was found.

Uncertainties

Sources

Independent performance sources (counted)

Other sources (not counted)

Not counted

Decision records: 0041; 0051 (grade-A basis check).