updated 2026-10-09 08:15 UTC

STORM

Repository Website

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

Research & Data Python Needs review MIT

Is STORM safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.2 / 10
Provenance None
Signed commits 33%
Last push 374d ago
Advisories None known
Compare STORM

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

Pick any agent to compare →
Suggest a correction

In detail: STORM scores 33.4/100 (Grade D), ranked #1280 of 1371 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; no published advisory affects its latest release (knowledge-storm); last pushed 2025-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How STORM could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-09-30)

Chain of custody

Scanners check what the code says. This traces who ships STORM and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/stanford-oval/storm, MIT, last pushed 2025-09-30. 33% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.2/10 (scanned Oct 5, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Linked, not attested

    • PyPI knowledge-storm Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: knowledge-storm 1.1.1. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of STORM.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues STORM’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How STORM compares in Research & Data

  1. #27 Open Deep Research (dzhng) 34.9 +1.5
  2. #28 Tongyi DeepResearch 34.2 +0.8
  3. #29 STORM 33.4 this agent
  4. #30 MindSearch 27.5 −5.9
  5. #31 SoL-Pi 23.3 −10.1

Bars show each HVTrust score; the tick marks STORM’s 33.4.

Where the 33.4 comes from

HVTrust dimensions vs the Research & Data average

33.4 / 100 · 100.0% confidence

STORM Research & Data average (37 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
2.2 below avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
11.2 / 17
in line with avg 11.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.7 below avg 12.7
AdoptionLog-scaled stars · package downloads
14.0 / 20
3.5 above avg 10.5

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-01
Rank Moved
Rank dropped 165 spots (#1113 → #1278)
2026-10-01
HVTrust Changed
HVTrust down 10.0pts (43.3 → 33.3)
2026-09-30
Warning Issued
Warning: eligibility issues detected
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 374 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-09-30)
Compare with another agent Get email alerts for STORM View Research & Data Report missing data
43.2
Activity sub-score · out of 100
#29
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 →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 374 days ago — may be stale

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
31.6k
Forks
3.0k
Last Push
2025-09-30
374 days ago
Commits (4 wk)
0
Downloads (7d)
246
pypi
HN mentions (30d)
4
Open Issues
61
Rank Change
=
was #1280

Analysis

Activity Inputs

43.2 / 100
StarsRepository reach
27.0 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.2 / 20

Common questions about STORM

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 374 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
Rank 30Warning Issued 1HVTrust 1
2026-10-01
Rank Moved
Rank dropped 165 spots (#1113 → #1278)
2026-10-01
HVTrust Changed
HVTrust down 10.0pts (43.3 → 33.3)
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-23
Rank Moved
Rank dropped 624 spots (#464 → #1088)
2026-09-22
Rank Moved
Rank dropped 96 spots (#368 → #464)
2026-09-21
Rank Moved
Rank rose 718 spots (#1086 → #368)
2026-09-12
Rank Moved
Rank dropped 14 spots (#1067 → #1081)
2026-09-09
Rank Moved
Rank dropped 11 spots (#1052 → #1063)
2026-09-07
Rank Moved
Rank dropped 34 spots (#1013 → #1047)
2026-09-06
Rank Moved
Rank dropped 14 spots (#999 → #1013)
2026-09-05
Rank Moved
Rank dropped 40 spots (#959 → #999)
2026-09-04
Rank Moved
Rank dropped 30 spots (#929 → #959)
2026-09-03
Rank Moved
Rank dropped 78 spots (#851 → #929)
2026-09-02
Rank Moved
Rank dropped 38 spots (#813 → #851)
2026-09-01
Rank Moved
Rank dropped 29 spots (#784 → #813)
2026-08-31
Rank Moved
Rank dropped 32 spots (#752 → #784)
2026-08-30
Rank Moved
Rank dropped 23 spots (#729 → #752)
2026-08-29
Rank Moved
Rank dropped 48 spots (#681 → #729)
2026-08-28
Rank Moved
Rank dropped 23 spots (#658 → #681)
2026-08-27
Rank Moved
Rank dropped 18 spots (#640 → #658)
2026-08-26
Rank Moved
Rank dropped 100 spots (#540 → #640)
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)
GitHub → Website → PyPI: knowledge-storm

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 33.4 Grade D
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.4 · Raw JSON