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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed 13 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
45.7k
Forks
4.5k
Last Push
2026-05-22
13 days ago
Commits (4 wk)
5
Downloads (7d)
190,430
pypi
HN mentions (30d)
174
Open Issues
1593
Rank Change
▼12
was #111
Analysis
HVTrust Dimensions
60.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.7 / 17
MaintenanceFreshness and commits
14.2 / 20
AdoptionStars and downloads
18.2 / 20
Activity Inputs
78.0 / 100
StarsRepository reach
28.0 / 30
FreshnessLast push recency
23.2 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
17.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
via deps.dev · OpenSSF
Signed Commits
16%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests10
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Aider safe?
Aider has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
Maintained. Last push was 13 days ago.
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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Aider?
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.
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.
