Is RA.Aid safe to use?

RA.Aid has an HVTrust score of 39.8/100 (Grade D), ranked #1181 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for RA.Aid?

RA.Aid scores 39.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.2k GitHub stars and is categorized under Coding Agents.

RA.Aid

Repository Website

Develop software autonomously.

Coding Agents Python Listed Apache-2.0

Is RA.Aid safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.1 / 10

Provenance None

Signed commits 17%

Last push 252d ago

Advisories None known

Compare RA.Aid

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Suggest a correction

In detail: RA.Aid scores 39.8/100 (Grade D), ranked #1181 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.1/10; 17% of recent commits are signed; no published advisory affects its latest release (ra-aid); last pushed 2026-01-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How RA.Aid 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.

Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 54.5 C · #50 of 77
Raise the OSSF Scorecard from 4.1 to 9.0lowest checks: CI-Tests 0, CII-Best-Practices 0, Fuzzing 0 +10.2 → 50.0 C · #56 of 77
Sign every commit17% signed today +4.1 → 43.9 D · #61 of 77

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships RA.Aid 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.

Source Partly signed

github.com/ai-christianson/RA.Aid, Apache-2.0, last pushed 2026-01-30. 17% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.1/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 0

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Linked, not attested
- PyPI ra-aid Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: ra-aid 0.30.2. No published advisory affects 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 RA.Aid.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions

Verify this score yourself

Every build re-issues RA.Aid’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 RA.Aid compares in Coding Agents

Bars show each HVTrust score; the tick marks RA.Aid’s 39.8.

Where the 39.8 comes from

HVTrust dimensions vs the Coding Agents average

39.8 / 100 · 100.0% confidence

RA.Aid Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

6.0 / 25

2.8 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

12.0 / 17

in line with avg 11.6

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.4 below avg 14.4

AdoptionLog-scaled stars · package downloads

11.6 / 20

in line with 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-23

Rank Moved

Rank dropped 648 spots (#520 → #1168)

2026-09-22

Rank Moved

Rank dropped 130 spots (#390 → #520)

2026-09-21

Rank Moved

Rank rose 779 spots (#1169 → #390)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.1/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 252 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for RA.Aid View Coding Agents Report missing data

30.9

Activity sub-score · out of 100

#66

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 D 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 (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars

2.2k

Forks

211

Last Push

2026-01-30

252 days ago

Commits (4 wk)

Downloads (7d)

437

pypi

HN mentions (30d)

Open Issues

Rank Change

▲2

was #1183

Analysis

Activity Inputs

30.9 / 100

StarsRepository reach

20.1 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.8 / 20

Common questions about RA.Aid

Public trust evidence for RA.Aid 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 RA.Aid publish package provenance?

No published build provenance is currently detected for RA.Aid. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does RA.Aid have an OpenSSF Scorecard?

RA.Aid has an OpenSSF Scorecard score of 4.1/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 RA.Aid actively maintained?

Stale. The repository has not been pushed to in 252 days. Consider whether the project is still being maintained.

What license does RA.Aid use?

RA.Aid ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are RA.Aid's commits signed?

17% of the last 100 commits to RA.Aid 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

8 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

2 tags

Broad capability areas detected.

code
search

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 RA.Aid'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-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependencies: DeepSeek, Multi-provider (LiteLLM), OpenRouter

Maintain RA.Aid?

For maintainers

HVTrust scores RA.Aid 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

Reputation Timeline

Signal history

2026-09-23

Rank Moved

Rank dropped 648 spots (#520 → #1168)

2026-09-22

Rank Moved

Rank dropped 130 spots (#390 → #520)

2026-09-21

Rank Moved

Rank rose 779 spots (#1169 → #390)

2026-09-12

Rank Moved

Rank dropped 10 spots (#1155 → #1165)

2026-09-09

Rank Moved

Rank dropped 13 spots (#1139 → #1152)

2026-09-07

Rank Moved

Rank dropped 17 spots (#1114 → #1131)

2026-09-06

Rank Moved

Rank dropped 15 spots (#1099 → #1114)

2026-09-05

Rank Moved

Rank dropped 38 spots (#1061 → #1099)

2026-09-04

Rank Moved

Rank dropped 18 spots (#1043 → #1061)

2026-09-03

Rank Moved

Rank dropped 57 spots (#986 → #1043)

2026-09-02

Rank Moved

Rank dropped 43 spots (#943 → #986)

2026-09-01

Rank Moved

Rank dropped 39 spots (#904 → #943)

2026-08-31

Rank Moved

Rank dropped 33 spots (#871 → #904)

2026-08-30

Rank Moved

Rank dropped 38 spots (#833 → #871)

2026-08-29

Rank Moved

Rank dropped 47 spots (#786 → #833)

2026-08-28

Rank Moved

Rank dropped 23 spots (#763 → #786)

2026-08-27

Rank Moved

Rank dropped 27 spots (#736 → #763)

2026-08-26

Rank Moved

Rank dropped 99 spots (#637 → #736)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-10

Rank Moved

Rank dropped 21 spots (#613 → #634)

2026-08-08

Rank Moved

Rank dropped 216 spots (#392 → #608)

2026-07-29

Rank Moved

Rank dropped 10 spots (#369 → #379)

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependencies: DeepSeek, Multi-provider (LiteLLM), OpenRouter

2026-07-15

Rank Moved

Rank dropped 27 spots (#328 → #355)

2026-07-14

Rank Moved

Rank dropped 19 spots (#309 → #328)

2026-07-13

Rank Moved

Rank dropped 36 spots (#273 → #309)

GitHub → Website → PyPI: ra-aid

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/ra-aid.svg)](https://hvtracker.net/agents/ra-aid)
            
HTML:
            <a href="https://hvtracker.net/agents/ra-aid"><img src="https://hvtracker.net/badge/ra-aid.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
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

RA.Aid

How RA.Aid could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How RA.Aid compares in Coding Agents

Where the 39.8 comes from

HVTrust dimensions vs the Coding Agents average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about RA.Aid

AI agent surface

Maintain RA.Aid?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Coding Agents