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 13 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
21.2k
Forks
4.9k
Last Push
2026-05-22
13 days ago
Commits (4 wk)
0
Downloads (7d)
50,639
pypi
HN mentions (30d)
242
Open Issues
150
Rank Change
▼9
was #109
Analysis
HVTrust Dimensions
60.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.4 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.9 / 17
MaintenanceFreshness and commits
11.1 / 20
AdoptionStars and downloads
16.7 / 20
Activity Inputs
66.5 / 100
StarsRepository reach
26.0 / 30
FreshnessLast push recency
23.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
17.2 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.2 / 10
via deps.dev · OpenSSF
Signed Commits
59%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection8
CI-Tests1
CII-Best-Practices0
Code-Review9
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained0
Packaging10
Pinned-Dependencies6
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Rasa safe?
Rasa 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 Rasa publish package provenance?
No published build provenance is currently detected for Rasa. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Rasa have an OpenSSF Scorecard?
Rasa has an OpenSSF Scorecard score of 5.2/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 Rasa actively maintained?
Maintained. Last push was 13 days ago.
What license does Rasa use?
Rasa ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Rasa's commits signed?
59% of the last 100 commits to Rasa 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 Rasa?
HVTrust scores Rasa 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.
