Is STORM safe?
STORM scores 44.2/100 (Grade D), ranked #262 of 328 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 3.2/10;
33% of recent commits are signed;
last pushed 2025-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
44.2/100 · Grade D
Strongest Signal
Adoption
15.2/20
Weakest Signal
Maintenance
0/20
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-24
Rank Moved
Rank dropped 32 spots (#236 → #268)
2026-06-23
Rank Moved
Rank dropped 18 spots (#218 → #236)
2026-06-22
Rank Moved
Rank dropped 11 spots (#207 → #218)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 3.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signalsThe repo was last pushed 284 days ago. Fresh activity helps separate stable projects from stale ones.
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. 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 →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed 284 days ago — may be stale
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
30.0k
Forks
2.8k
Last Push
2025-09-30
284 days ago
Commits (4 wk)
0
Downloads (7d)
2,214
pypi
HN mentions (30d)
2
Open Issues
59
Rank Change
▲1
was #263
Analysis
HVTrust Dimensions
44.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.7 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.2 / 17
MaintenanceFreshness and commits
0.0 / 20
AdoptionStars and downloads
15.2 / 20
Activity Inputs
42.9 / 100
StarsRepository reach
26.9 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.2 / 10
OpenSSF Scorecard · scanned Jul 8, 2026
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
Vulnerabilities7
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.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 STORM actively maintained?
Stale. The repository has not been pushed to in 284 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.
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 →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
database
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
How this surface has changed
Detected changes to STORM'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.
Runtime surface grew — new detected provider dependencies: OpenAI, Qdrant
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.
