Ragas
Website
Supercharge Your LLM Application Evaluations 🚀
Is Ragas safe? Thin or incomplete trust evidence. Review carefully before production use. One published advisory affects its latest release.
Compare Ragas
How does it stack up against its Observability & Evaluation neighbours?
Pick any agent to compare →In detail: Ragas scores 53.6/100 (Grade C), ranked #846 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.4/10; 100% of recent commits are signed; 1 published advisory affects its latest release (ragas); last pushed 2026-02-24. 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: ragas 0.4.3. 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 RAGAS has SSRF via Multi-Modal Faithfulness Collections Module
How Ragas 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 → 68.3 B · #11 of 26
- Raise the OSSF Scorecard from 4.4 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Dependency-Update-Tool 0 +9.6 → 63.2 C · #14 of 26
Chain of custody
Scanners check what the code says. This traces who ships Ragas 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 Signed
github.com/vibrantlabsai/ragas, Apache-2.0, last pushed 2026-02-24. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.4/10 (scanned Sep 30, 2026). The checks that decide who can get a change released:
- Code Review4
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions7
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 9CII-Best-Practices 0Code-Review 4Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 0Fuzzing 0License 10Maintained 0Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 7Vulnerabilities 10 -
Published packages Linked, not attested
- PyPI ragas 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 1 advisory
Latest release checked: ragas 0.4.3. 1 published advisory affects it (OSV, checked 2026-10-09).
Changes to this chain
- 2026-10-02 Provenance drift warning cleared (now: unknown)
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 Ragas’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.
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 Ragas compares in Observability & Evaluation
- #16 Traceroot 59.8 +6.2
- #17 agentacct 55.7 +2.1
- #18 Ragas 53.6 this agent
- #19 AgentOps 53.6 ±0
- #20 TruLens 47.3 −6.3
Bars show each HVTrust score; the tick marks Ragas’s 53.6.
Where the 53.6 comes from
HVTrust dimensions vs the Observability & Evaluation average
53.6 / 100 · 100.0% confidenceRagas Observability & Evaluation average (26 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 (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
40.3 / 100Common questions about Ragas
Does Ragas publish package provenance?
Does Ragas have an OpenSSF Scorecard?
Is Ragas actively maintained?
What license does Ragas use?
Are Ragas'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
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Ragas'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 Ragas?
For maintainers
HVTrust scores Ragas 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/ragas)
<a href="https://hvtracker.net/agents/ragas"><img src="https://hvtracker.net/badge/ragas.svg" alt="HVTrust"></a>
Other agents in Observability & Evaluation
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