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 247 days ago — may be stale
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
28.3k
Forks
2.6k
Last Push
2025-09-30
247 days ago
Commits (4 wk)
0
Downloads (7d)
654
pypi
HN mentions (30d)
1
Open Issues
94
Rank Change
▼6
was #162
Analysis
HVTrust Dimensions
42.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.3 / 17
MaintenanceFreshness and commits
0.0 / 20
AdoptionStars and downloads
14.4 / 20
Activity Inputs
42.6 / 100
StarsRepository reach
26.7 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
15.9 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.3 / 10
via deps.dev · OpenSSF
Signed Commits
33%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection1
CI-Tests0
CII-Best-Practices0
Code-Review4
Contributors3
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities8
Is STORM safe?
Public trust evidence for STORM 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 STORM publish package provenance?
No published build provenance is currently detected for STORM. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does STORM have an OpenSSF Scorecard?
STORM has an OpenSSF Scorecard score of 3.3/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 STORM actively maintained?
Stale. The repository has not been pushed to in 247 days. Consider whether the project is still being maintained.
What license does STORM use?
STORM ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are STORM's commits signed?
33% of the last 100 commits to STORM 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 STORM?
HVTrust scores STORM 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.
