Skip to content

Standard

OSV

OSV is an open, machine-readable schema and database for tracking security vulnerabilities and malware advisories in open-source software.

Known aliases

  • Open Source Vulnerabilities
  • Open Source Vulnerability
  • Open Source Vulnerability format
  • OSV Actor
  • OSV advisory
  • OSV.dev
  • OSV npm malware advisories
  • OSV records

Current stories

buildOne report1 publisher

Databricks' LLM triage stops short of a malicious verdict on 14.4% of npm malware that bundles a binary

Databricks says its LLM pipeline fails to reach a decisive malicious verdict on 14.4% of npm malware that bundles a binary, against 6.2% for source-only packages. Those binary packages are 432 of 11,413 scanned versions, and Databricks tests feeding the model pre-computed static evidence as the fix.

Publishers:databricks.com

Reality

Evidence50
Adoption
Not scored
Hype gap+15
Incentives60
Confidence55
buildOne report1 publisher

Open WebUI's 0.11.4 security fixes were still missing from GitHub and OSV advisory records on 11 October

At least 15 Open WebUI advisories fixed in 0.11.4, one a CVSS 8.1 session-token theft, were missing from GitHub's advisory database and OSV on 11 October. Scanners reading those databases can report 0.11.1 to 0.11.3 as clean, a dev.to post found, so operators have to check the version themselves.

Publishers:dev.to

Reality

Evidence48
Adoption
Not scored
Hype gap+12
Incentives55
Confidence42
securityConfirmed3 publishers

Checkmarx finds malicious npm package function-flag still installable after 37,000 downloads

Checkmarx says function-flag, malicious since July 2025 and downloaded more than 37,000 times, is still on npm with no advisory flagging it. Advisory-based scanners have nothing to match, so finding it means checking lockfiles for the campaign's eight names.

Perspective Coverage

3 publishers
Builder
Builder 43%
Operator
Operator 50%
Investor
Investor 7%

Reality

Evidence70
Adoption20
Hype gap+15
Incentives55
Confidence68
buildOne report1 publisher

WorldScript Studio gives merge-blocking power to four of its fifteen automated reviewers

WorldScript Studio tracks fifteen automated reviewers in a JSON registry, and only four deterministic security scanners may block a merge. The design keeps LLM false positives off the merge path and keeps pull-request code away from the checker that judges it.

Publishers:dev.to

Reality

Evidence50
Adoption
Not scored
Hype gap+10
Incentives55
Confidence45
securityOne report1 publisher

Chainguard opens Athena's 40,000-finding backlog on September 28 with fifty silent fixes

Chainguard says fix generation was never its bottleneck and that responsible disclosure at scale is, so its first public batch is built from bugs upstreams quietly fixed years ago and never filed CVEs for.

Publishers:chainguard.dev

Reality

Evidence34
Adoption16
Hype gap+28
Incentives82
Confidence48
buildOne report1 publisher

Eighteen flagged agent packages still install from npm weeks after the feeds listed them

AgentGate read the shipped code behind 30-plus OSV and GHSA flags, verified 19 npm packages as malicious, and found 18 still resolvable on publication day. Removal, not detection, is where the chain stopped.

Publishers:dev.to

Reality

Evidence48
Adoption20
Hype gap+22
Incentives78
Confidence55
securityOne report1 publisher

Consuming a malware feed at GitHub's scale bills out in rip-outs and credential rotation

The engineer running Dependabot across 30 million repositories says wiring in OpenSSF's malicious-package feed was the cheap part, while normalization ate the budget and each alert ends in a build-credential incident.

Reality

Evidence46
Adoption62
Hype gap−12
Incentives64
Confidence52
buildOne report1 publisher

Layered permissions, not just three GitHub tools, secure this dependency scanner

An Apify Actor read a manifest, queried OSV, and filed one triage issue, with no branch or merge rights anywhere in its schema. The run that mattered was the second one, which updated the issue instead of filing a duplicate.

Publishers:dev.to

Reality

Evidence46
Adoption12
Hype gap+12
Incentives74
Confidence52
buildOne report1 publisher

A fabrication checker cleared an invented CVE because it asked the wrong question

CVE-2026-45871 was made up for a test and turned out to exist. The check resolved it against a global namespace rather than against the project it was meant to defend.

Publishers:dev.to

Reality

Evidence58
Adoption10
Hype gap−18
Incentives40
Confidence52
productOne report1 publisher

AI writes the Dockerfile, and the pipeline is still checking the app code

Two 2026 studies put AI-generated deployment infrastructure at worse than a coin flip, and the gates most CI pipelines run were built for application source, not config.

Publishers:devops.com

Reality

Evidence58
Adoption52
Hype gap+12
Incentives66
Confidence57
securityOne report1 publisher

Vulnerability disclosures bent upward in 2026. Algorithm records did not.

METR's public discovery series shows a sharp 2026 slope change in vulnerability reports, no comparable change across seven optimization benchmarks, and slower growth in the exploited-bug catalogues.

Publishers:metr.org

Reality

Evidence58
Adoption44
Hype gap+9
Incentives32
Confidence55
buildOne report1 publisher

Existence checks are dead: attackers now register the packages your AI invents

A single-author npm tool measured what supply-chain guards actually verify, and found documented hallucinated names alive on the registry. Provenance beats resolution.

Publishers:dev.to

Reality

Evidence42
Adoption12
Hype gap+18
Incentives76
Confidence46
buildOne report1 publisher

The npm audit that works because it never installs the package

A dev.to walkthrough puts metadata and tarball inspection first, on the grounds that most npm malware fires during install and not at import. It needs nothing you have to buy.

Publishers:dev.to

Reality

Evidence46
Adoption
Not scored
Hype gap+12
Incentives30
Confidence55