Source of truth

Every Erydas finding starts on OSV.

Open Source Vulnerabilities is the open, precise, distributed database for disclosed advisories — including CVEs, GHSAs, and MAL supply-chain malware records. Erydas matches your lockfile to OSV, then plans the smallest verified fix. No invented CVEs. No opaque scores.

  • Open

    Advisories from authoritative open sources — GitHub, OpenSSF Malicious Packages, PyPA, RustSec, and more.

  • Precise

    Machine-readable affected ranges that map to exact package versions and commits.

  • Actionable

    Erydas turns OSV disclosure into a minimum safe bump — then rescans to prove it.

Partnership

Why Eridas uses OSV

Eridas is AI-first dependency security — but advisory truth is never invented. is the disclosed-vulnerability source of truth: open data, precise version ranges, and a distributed model that scales from a single repo to every agent and API consumer on Eridas Cloud.

  • Open

    Advisories from authoritative open sources — GitHub Security Advisories, PyPA, RustSec, Go, and more. Anyone can inspect the data and contribute fixes upstream.

  • Precise

    Machine-readable affected ranges map to exact package versions, commits, and ecosystems. Eridas queries OSV with the same (ecosystem, name, version) tuples your lockfile already pins.

  • Distributed

    No single vendor lock-in. OSV aggregates disclosed advisories across ecosystems so agents, CI, and humans share one advisory truth — the same records Eridas surfaces in CLI, Cloud, and MCP.


How Eridas uses OSV

The pipeline is deterministic end to end — CLI, Cloud API, SDK, MCP, and UIs all run the same scan contract. Optional AI may explain findings; it never invents vulnerabilities or chooses fixed versions.

Lockfile →→ plan → approve → apply → verify

osv.dev
  1. 01

    Lockfile

    Exact installed versions

  2. 02

    Disclosed advisories

  3. 03

    Plan

    Minimum safe bump

  4. 04

    Approve

    TTY, --yes, or --force

  5. 05

    Apply

    Scripts disabled

  6. 06

    Verify

    Rescan + checks

  1. 01

    Read the lockfile

    Eridas loads package-lock.json and inventories every exact installed version — direct and transitive. The lockfile decides what is installed; OSV does not guess from semver ranges alone.

  2. 02

    Query OSV

    Batched (ecosystem, name, version) queries hit the OSV API. Each hit loads advisory id, aliases, severity, summary, fixed versions, and references. Unknown-severity advisories stay visible.

  3. 03

    Plan the fix

    For direct dependencies, Eridas picks the minimum fixed version that closes every advisory for that package — preserving caret/tilde style and blocking major bumps unless you opt in.

  4. 04

    Verify with rescan

    After apply, Eridas regenerates the lockfile with scripts disabled, rescans against OSV, and runs configured checks. Any failure restores both package.json and the lockfile.

What Eridas does not do

ApproachEridas
Invent CVEs or hallucinate vulnsNever — OSV disclosures only
Opaque proprietary scoresOSV severity + explicit advisory text
Forum scraping or leak sitesOut of scope
Let AI pick fixed versionsDeterministic planner from OSV fixed versions

OSV resources

Explore the database, read the schema, or call the API directly — the same surfaces Eridas uses under the hood.

  • osv.dev — browse disclosed advisories
  • OSV API — query by package version
  • OSV schema — machine-readable advisory format