How to Use OSV.dev dependency vulnerability check in VS Code
Check multiple package versions or Git commits together and receive matching vulnerability IDs and modification times. Use it to screen a dependency inventory before fetching advisory details.
Prompts to try with OSV.dev dependency vulnerability check in VS Code
Copy an example into VS Code, or ask in your own words.
Use OSV.dev dependency vulnerability check for the resolved npm package versions in package-lock.json, including lodash if present. Write a report linking each affected dependency to its returned vulnerability IDs.
Use OSV.dev dependency vulnerability check to compare npm lodash 4.17.15 and 4.17.21. Add the returned vulnerability IDs and modification times to this project's dependency review notes.
Use OSV.dev dependency vulnerability check to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from OSV.dev dependency vulnerability check and tell me what changed since last week.
Check OSV.dev dependency vulnerability check and summarize what you find in three bullet points.
How to set up OSV.dev dependency vulnerability check in VS Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the hosted server
Use Add to VS Code on the console's Agents & MCP page, or run:
code --add-mcp '{"name":"spiral","type":"http","url":"https://api.spiral.ai/mcp"}' - Sign in
VS Code asks you to sign in when it first starts the server: sign in to Spiral and click Authorize. No API key. Run MCP: List Servers from the Command Palette to check that Spiral is running.
Use the Spiral skill
- Send VS Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run OSV.dev dependency vulnerability check
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "osv-dev/vulnerabilities/query_batch", "input": { "queries": [ {} ] } }'
Then paste one of the prompts above: VS Code finds OSV.dev dependency vulnerability check on Spiral, shows the price and runs it.
OSV.dev dependency vulnerability check providers and prices
Spiral runs OSV.dev dependency vulnerability check through Alexandria. Open a card for today's price, with every fee included.
What can you do with OSV.dev dependency vulnerability check in VS Code?
Turn dependency findings into a concrete upgrade review for your project. A coding agent can match installed versions to OSV.dev advisories and check proposed replacements before changing the dependency files.
Review dependencies before a release
Screen the release's package versions, investigate the returned advisory IDs, and check proposed replacement versions. Produce a review list with affected packages and supporting references.
Compare upgrade candidates
Check current and proposed versions together, inspect each candidate separately, and read the advisories behind remaining findings. Use the recorded affected ranges to explain what an upgrade addresses.
Investigate a reported vulnerability
Read the reported advisory, check the relevant package version, and screen other deployed versions of that package. Summarize the affected versions and the source's remediation information.
Maintain a dependency review queue
Recheck an inventory on a schedule and compare vulnerability IDs and modification times. Investigate changed records and check individual packages before updating the review queue.
Prepare a software security assessment
Screen a product's declared package versions, investigate individual dependency matches, and collect advisory references. Build an assessment grounded in recorded package impact.
Validate a dependency change
Compare the package versions before and after a change, check each affected dependency, and inspect the underlying advisories. Explain which recorded findings disappear and which remain.
More on OSV.dev dependency vulnerability check and VS Code
Overview
OSV.dev dependency vulnerability check in other agents
Questions about OSV.dev dependency vulnerability check in VS Code
Can VS Code use OSV.dev dependency vulnerability check?
Yes. Add Spiral to VS Code as an MCP server, and VS Code can find and run OSV.dev dependency vulnerability check like any built-in tool.
How much does OSV.dev dependency vulnerability check cost in VS Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your VS Code plan is separate.
Do I need an Alexandria account to use OSV.dev dependency vulnerability check in VS Code?
No. Spiral runs OSV.dev dependency vulnerability check on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up OSV.dev dependency vulnerability check in VS Code?
About two minutes: add the hosted server, then sign in.
Does VS Code wait while OSV.dev dependency vulnerability check runs?
OSV.dev dependency vulnerability check runs in the background. VS Code starts the run, checks on it and gives you the json when it's ready.
Which open source ecosystems does OSV.dev cover?
Coverage includes npm, PyPI, Maven, Go, crates.io, and RubyGems, along with Git repositories and distributions such as Debian, Alpine, and Ubuntu. OSV.dev combines advisory databases rather than relying on one publisher.
How quickly does OSV.dev reflect advisory updates?
OSV.dev targets source data being no more than 15 minutes stale 99.5% of the time. That measures freshness relative to its sources, not the time between discovering a vulnerability and publishing it.
Does an affected package mean my application is exploitable?
OSV.dev's minimum precision standard is package-level matching. Symbol-level information depends on what the advisory supplies, so a package match alone does not establish whether your application reaches the vulnerable code.
Why do some advisories lack severity or remediation details?
The OSV schema makes severity, descriptions, references, and affected-package information optional. A record can therefore exist without a severity assessment or a documented fixed version.
Can OSV.dev still return a withdrawn advisory?
Yes. Withdrawn records disappear from package and batch query results but remain available through the individual vulnerability lookup.
Start using OSV.dev dependency vulnerability check in VS Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into VS Code:
set up https://spiral.ai/SKILL.md


