Does OpenClaw really have 591 security advisories — more than all of Rust?

OSV lists exactly 591 advisories for npm openclaw in 2026, more than Rust on the same GHSA cut (536 in 2026; the post's OSV crates.io figure was 483). The GitHub repo's own published-advisory list is larger (722) because it is a different scope.

Score

10.0/10

claims that held up

Verdict

Reproduced

3

Access needed

L0 Public web only

Run 27 Oct 2026

We re-ran it and got the claimed kind of result, checked against ground truth.

3

claims scored

all tested

3 of 3

held up in full

3

sites and APIs touched

about 2 minutes

run time

Claim by claim

OpenClaw (npm) has 591 advisories in 2026coreHeld up

OSV npm openclaw returned exactly 591 vulns with 2026 published field.

591 is more than all of RustcoreHeld up

591 > 536 GHSA ecosystem=rust published in 2026 (post's OSV crates.io figure was 483).

The project is openclaw npm / openclaw/openclawcoreHeld up

github.com/openclaw/openclaw and npm package openclaw resolve.

Open a claim to see what we checked.

Access it needs
L0 Public web only
Run on
27 Oct 2026, 08:19 to 08:21 (UTC+8)
Run by
Grok Bot
Check again by
26 Nov 2026

What was claimed

'AI bug hunters tripled open-source advisories in 2026. OpenClaw alone got 591, more than all of Rust.'

@MattBusel on X. Original post

What we found

Held up. OSV lists exactly 591 advisories for npm openclaw in 2026. That is more than Rust on the same GHSA cut (536 in 2026; the post's OSV crates.io figure was 483). The GitHub repo's own published-advisory list is larger (722) because it is a different scope than the OSV npm package count.

How we checked it

OSV and GitHub API responses saved under runs/2026-10-27/openclaw-security-advisories-count/. Answer key written before the run.

What the agent did

  1. OSV.dev: npm package openclaw → 591 vulns (all with 2026 published field)
  2. GitHub API: openclaw/openclaw security-advisories → 722 published (8 pages)
  3. GitHub Advisory Database: ecosystem=rust, published in 2026 → 536
  4. Confirmed repo openclaw/openclaw and npm name openclaw

Sites and APIs touched: osv.dev, api.github.com, github.com/openclaw/openclaw.

Where it went wrong

  • GitHub repo security-advisories (722) is not the same metric as OSV npm (591); readers should not mix them.
  • 'All of Rust' can mean crates.io OSV or GHSA ecosystem=rust; we checked both and both sit below 591.

Try it yourself

Exact prompt we used
How many security advisories does the OpenClaw npm package have in 2026, and how does that compare to all of Rust (crates.io)? Cite OSV.dev or GitHub Advisory Database.

Lowest-access way to try it

L0. Ask the agent to query OSV for the exact package and ecosystem, and to say which Rust count it used (OSV crates.io vs GHSA).

Run details

Status
Reproduced (V2)
Access level used
L0: No account access
Original post's setup
L0
Method
Queried OSV for every vulnerability on the npm package openclaw, paged the GitHub repo security-advisories list for openclaw/openclaw, and counted 2026 GitHub Advisory Database entries for ecosystem=rust. Compared each number with the post.
Run by
Grok Bot (this assistant) on its own Linux computer with web search/fetch/shell/browser tools; this run: OSV.dev query for npm package openclaw, GitHub security-advisories for openclaw/openclaw, GitHub Advisory Database ecosystem=rust for 2026
Agent in the original post
Not stated in our record
Run date
2026-10-27 (UTC+8)
Time
About 2 minutes (08:19:30-08:21:02 UTC+8)
Cost
Not metered (subscription agent); no paid APIs, no purchases
Re-verify by
2026-11-26

How to cite

TriedAgents, "Does OpenClaw really have 591 security advisories — more than all of Rust?", reproduced, checked 2026-10-27, https://triedagents.com/cases/openclaw-security-advisories-count/

Get one re-run case every weekday

One agent use case we actually re-ran, every weekday. Free.

We only store your email address. Every issue has a one-click unsubscribe link. Privacy