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 20:15 UTC·Repo last pushed 100 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
14.2k
Forks
1.5k
Last Push
2026-02-24
100 days ago
Commits (4 wk)
0
Downloads (7d)
362,284
pypi
HN mentions (30d)
7
Open Issues
424
Rank Change
▼9
was #125
Analysis
HVTrust Dimensions
56.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.2 / 17
MaintenanceFreshness and commits
5.3 / 20
AdoptionStars and downloads
17.4 / 20
Activity Inputs
50.7 / 100
StarsRepository reach
24.9 / 30
FreshnessLast push recency
11.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.7 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.4 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests9
CII-Best-Practices0
Code-Review4
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions7
Vulnerabilities10
Is Ragas safe?
Ragas 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 Ragas publish package provenance?
No published build provenance is currently detected for Ragas. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ragas have an OpenSSF Scorecard?
Ragas has an OpenSSF Scorecard score of 4.4/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 Ragas actively maintained?
Slowing down. Last push was 100 days ago — keep an eye on whether activity resumes.
What license does Ragas use?
Ragas ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ragas's commits signed?
100% of the last 100 commits to Ragas 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 Ragas?
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.
