updated 2026-10-09 08:15 UTC

Aider

Repository Website

aider is AI pair programming in your terminal

Coding Agents Python Listed Apache-2.0

Is Aider safe? Thin or incomplete trust evidence. Review carefully before production use. 2 published advisories affect its latest release.

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 16%
Last push 140d ago
Advisories 2, worst low
Compare Aider

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Aider scores 51.2/100 (Grade C), ranked #929 of 1371 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; 2 published advisories affect its latest release (aider-chat); last pushed 2026-05-22. Every point is earned from checkable signals — never paid placement. How scoring works →

Known advisories

Published advisories (from OSV) that affect the release you'd install today: aider-chat 0.86.2. An unfixed critical advisory caps the HVTrust score at 64.9 (Grade C) and a high one at 79.9 (Grade B), until a fixed release ships; moderate, low and unrated ones are shown, not scored. Checked 2026-10-09.

  • LOW Aider is vulnerable to Code Injection via editor_coder.run function GHSA-7w7m-v5vp-w699 · CVE-2026-10175 · aider-chat 0.86.2 · published 2026-05-31
  • LOW Aider has an SSRF vulnerability through its AWS EC2 Metadata Endpoint GHSA-hchg-qm84-cj9p · CVE-2026-10177 · aider-chat 0.86.2 · published 2026-05-31

How Aider could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Aider and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Aider-AI/aider, Apache-2.0, last pushed 2026-05-22. 16% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Jul 11, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI aider-chat Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today 2 advisories

    Latest release checked: aider-chat 0.86.2. 2 published advisories affect it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Aider.

Evidence behind this score

Coverage A: 5 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions
  • Community mentions

Verify this score yourself

Every build re-issues Aider’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Aider compares in Coding Agents

  1. #51 SWE-AF 52.9 +1.7
  2. #52 Grok Build 51.8 +0.6
  3. #53 Aider 51.2 this agent
  4. #54 Whale 50.9 −0.3
  5. #55 Roo Code 50.4 −0.8

Bars show each HVTrust score; the tick marks Aider’s 51.2.

Where the 51.2 comes from

HVTrust dimensions vs the Coding Agents average

51.2 / 100 · 100.0% confidence

Aider Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.5 / 25
3.3 below avg 8.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
in line with avg 11.6
Maintenance60% last-push freshness · 40% commit activity
2.7 / 20
11.7 below avg 14.4
AdoptionLog-scaled stars · package downloads
17.6 / 20
5.7 above avg 11.9

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-30
Rank Moved
Rank dropped 10 spots (#884 → #894)
2026-09-28
Rank Moved
Rank dropped 10 spots (#870 → #880)
2026-09-23
Rank Moved
Rank dropped 546 spots (#320 → #866)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 140 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Aider View Coding Agents Report missing data
51.1
Activity sub-score · out of 100
#53
In Coding Agents

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 →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 140 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
49.4k
Forks
5.0k
Last Push
2026-05-22
140 days ago
Commits (4 wk)
0
Downloads (7d)
55,648
pypi
HN mentions (30d)
93
Open Issues
1395
Rank Change
▼2
was #927

Analysis

Activity Inputs

51.1 / 100
StarsRepository reach
28.2 / 30
FreshnessLast push recency
5.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
17.2 / 20

Common questions about Aider

Public trust evidence for Aider is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Aider publish package provenance?
No published build provenance is currently detected for Aider. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Aider have an OpenSSF Scorecard?
Aider has an OpenSSF Scorecard score of 3.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Aider actively maintained?
Slowing down. Last push was 140 days ago — keep an eye on whether activity resumes.
What license does Aider use?
Aider ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Aider's commits signed?
16% of the last 100 commits to Aider are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
  • code
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-08-20
Activity Went Stale
No commits for 90 days
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

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.

Submit a correction → Add the trust badge

Public Actions

Actions (30d)
5323
Top repos (sampled)

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
Rank 30Surface 1Surface 1Stale 1
2026-09-30
Rank Moved
Rank dropped 10 spots (#884 → #894)
2026-09-28
Rank Moved
Rank dropped 10 spots (#870 → #880)
2026-09-23
Rank Moved
Rank dropped 546 spots (#320 → #866)
2026-09-22
Rank Moved
Rank dropped 12 spots (#308 → #320)
2026-09-21
Rank Moved
Rank rose 551 spots (#859 → #308)
2026-09-11
Rank Moved
Rank dropped 20 spots (#810 → #830)
2026-09-08
Rank Moved
Rank dropped 14 spots (#786 → #800)
2026-09-07
Rank Moved
Rank dropped 37 spots (#749 → #786)
2026-09-05
Rank Moved
Rank dropped 65 spots (#676 → #741)
2026-09-04
Rank Moved
Rank dropped 27 spots (#649 → #676)
2026-09-03
Rank Moved
Rank dropped 32 spots (#617 → #649)
2026-09-02
Rank Moved
Rank dropped 31 spots (#586 → #617)
2026-09-01
Rank Moved
Rank dropped 31 spots (#555 → #586)
2026-08-31
Rank Moved
Rank dropped 29 spots (#526 → #555)
2026-08-29
Rank Moved
Rank dropped 30 spots (#493 → #523)
2026-08-27
Rank Moved
Rank dropped 15 spots (#473 → #488)
2026-08-26
Rank Moved
Rank dropped 54 spots (#419 → #473)
2026-08-24
Rank Moved
Rank dropped 19 spots (#404 → #423)
2026-08-22
Rank Moved
Rank rose 15 spots (#420 → #405)
2026-08-20
Activity Went Stale
No commits for 90 days
2026-08-19
Rank Moved
Rank dropped 12 spots (#407 → #419)
2026-08-17
Rank Moved
Rank rose 12 spots (#418 → #406)
2026-08-16
Rank Moved
Rank dropped 10 spots (#408 → #418)
2026-08-13
Rank Moved
Rank dropped 15 spots (#389 → #404)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Rank Moved
Rank rose 21 spots (#410 → #389)
2026-08-10
Rank Moved
Rank dropped 18 spots (#391 → #409)
2026-08-08
Rank Moved
Rank dropped 93 spots (#286 → #379)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)
2026-07-17
Rank Moved
Rank dropped 11 spots (#238 → #249)
2026-07-15
Rank Moved
Rank dropped 11 spots (#225 → #236)
2026-07-14
Rank Moved
Rank dropped 25 spots (#200 → #225)
2026-07-13
Rank Moved
Rank dropped 17 spots (#183 → #200)
GitHub → Website → PyPI: aider-chat

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 51.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/aider.svg)](https://hvtracker.net/agents/aider)
HTML:
<a href="https://hvtracker.net/agents/aider"><img src="https://hvtracker.net/badge/aider.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
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.4 · Raw JSON