Aider
aider is AI pair programming in your terminal
Compare Aider
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →Thin or incomplete trust evidence. Review carefully before production use.
Is Aider safe? Aider scores 54.9/100 (Grade C), ranked #404 of 1308 tracked open-source AI agent projects, on evidence coverage A (5 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.8/10; 16% of recent commits are signed; last pushed 2026-05-22. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in Coding Agents
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (5 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
HVTrust Dimensions vs Coding Agents
54.9 / 100 · 100.0% confidenceAider Coding Agents average (70 agents)
Activity Inputs
57.2 / 100Supply Chain Trust
Is Aider safe?
Does Aider publish package provenance?
Does Aider have an OpenSSF Scorecard?
Is Aider actively maintained?
What license does Aider use?
Are Aider's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- code
- shell
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Aider's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Aider?
For maintainers
HVTrust scores Aider from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Public Actions
Action counts reflect activity on public repos where this agent left detectable fingerprints. Private repo usage is invisible. Counts are approximate (GitHub Search API caps at 1,000 results per query). Methodology described in the Provenance Profile spec.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/aider)
<a href="https://hvtracker.net/agents/aider"><img src="https://hvtracker.net/badge/aider.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API · GitHub Search API (fingerprint actions)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON