Is STORM safe to use?

STORM has an HVTrust score of 44.6/100 (Grade D), ranked #540 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for STORM?

STORM scores 44.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 31.1k GitHub stars and is categorized under Research & Data.

STORM

stanford-oval/storm

An LLM-powered knowledge curation system that researches a topic and generates a full-length report with citations.

Research & Data Python Grade D Listed MIT

44.6/100

Rank #540 of 1308

Compare STORM

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2025-09-30 · 329d ago

Recent change

Rank +1

Is STORM safe? STORM scores 44.6/100 (Grade D), ranked #540 of 1308 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 →

Ranked neighbours in Research & Data

#13 Lumibot — 55.5 (C) → #14 FinRobot — 50.9 (C) → #16 MiroThinker — 44.6 (D) → #17 auto-deep-researcher-24x7 — 41.6 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-24

Rank Moved

Rank dropped 11 spots (#531 → #542)

2026-08-22

Rank Moved

Rank rose 11 spots (#544 → #533)

2026-08-17

Rank Moved

Rank rose 10 spots (#543 → #533)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.2/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 329 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for STORM View Research & Data Report missing data

43.1

Activity sub-score · out of 100

#15

In Research & Data

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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

31.1k

Forks

2.9k

Last Push

2025-09-30

329 days ago

Commits (4 wk)

Downloads (7d)

2,214

pypi

HN mentions (30d)

Open Issues

Rank Change

▲2

was #542

Analysis

HVTrust Dimensions vs Research & Data

44.6 / 100 · 100.0% confidence

STORM Research & Data average (32 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.7 / 25

1.0 below avg 6.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

11.2 / 17

in line with avg 11.1

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.5 below avg 12.5

AdoptionLog-scaled stars · package downloads

15.2 / 20

4.2 above avg 11.0

Activity Inputs

43.1 / 100

StarsRepository reach

27.0 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

16.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.2 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

33%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 0

CII-Best-Practices 0

Code-Review 4

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 7

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 329 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.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

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.

External Service Dependencies

high confidence

3 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

database

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

Maintain STORM?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-24

Rank Moved

Rank dropped 11 spots (#531 → #542)

2026-08-22

Rank Moved

Rank rose 11 spots (#544 → #533)

2026-08-17

Rank Moved

Rank rose 10 spots (#543 → #533)

2026-08-13

Rank Moved

Rank dropped 12 spots (#523 → #535)

2026-08-12

Rank Moved

Rank rose 13 spots (#536 → #523)

2026-08-10

Rank Moved

Rank dropped 19 spots (#517 → #536)

2026-08-08

Rank Moved

Rank dropped 148 spots (#369 → #517)

2026-07-29

Rank Moved

Rank dropped 11 spots (#345 → #356)

2026-07-15

Rank Moved

Rank dropped 25 spots (#313 → #338)

2026-07-14

Rank Moved

Rank dropped 17 spots (#296 → #313)

2026-07-13

Rank Moved

Rank dropped 35 spots (#261 → #296)

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)

2026-06-21

Rank Moved

Rank dropped 13 spots (#194 → #207)

2026-06-18

Rank Moved

Rank dropped 11 spots (#177 → #188)

2026-06-02

Rank Moved

Rank dropped 12 spots (#149 → #161)

2026-06-01

Rank Moved

Rank dropped 17 spots (#132 → #149)

2026-05-29

Rank Moved

Rank dropped 20 spots (#115 → #135)

GitHub → PyPI: knowledge-storm

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/storm.svg)](https://hvtracker.net/agents/storm)
            
HTML:
            <a href="https://hvtracker.net/agents/storm"><img src="https://hvtracker.net/badge/storm.svg" alt="HVTrust"></a>

Other agents in Research & Data

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON