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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed today
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
24.8k
Forks
2.2k
Last Push
2026-06-04
today
Commits (4 wk)
929
Downloads (7d)
—
HN mentions (30d)
57
Open Issues
381
Rank Change
▼9
was #140
Analysis
HVTrust Dimensions
48.8 / 100 · 75.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.7 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
10.5 / 20
Activity Inputs
91.9 / 100
StarsRepository reach
26.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.9 / 10
via deps.dev · OpenSSF
Signed Commits
98%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection4
CI-Tests10
CII-Best-Practices0
Code-Review8
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License9
Maintained10
Packaging10
Pinned-Dependencies1
SAST7
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Mastra safe?
Public trust evidence for Mastra 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 Mastra publish package provenance?
No published build provenance is currently detected for Mastra. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Mastra have an OpenSSF Scorecard?
Mastra has an OpenSSF Scorecard score of 4.9/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 Mastra actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Mastra use?
Mastra ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mastra's commits signed?
98% of the last 100 commits to Mastra 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 Mastra?
HVTrust scores Mastra 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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OSSF Scorecard via deps.dev · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
