How to Use OSV.dev package vulnerability lookup in Amp
Find known vulnerabilities affecting one package version or Git commit, including affected ranges and advisory references when available. Use it to check a dependency or compare an upgrade candidate.
Prompts to try with OSV.dev package vulnerability lookup in Amp
Copy an example into Amp, or ask in your own words.
Use OSV.dev package vulnerability lookup to check npm lodash 4.17.15, then locate that dependency in this project and summarize the matching advisories.
Use OSV.dev package vulnerability lookup to compare PyPI jinja2 3.1.4 and 3.1.6. Check whether either version appears in this project's dependency files and propose a change based on the returned findings.
Use OSV.dev package vulnerability lookup to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from OSV.dev package vulnerability lookup and tell me what changed since last week.
Check OSV.dev package vulnerability lookup and summarize what you find in three bullet points.
How to set up OSV.dev package vulnerability lookup in Amp
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
No header and no client ID or secret: Amp registers itself with Spiral.
amp mcp add spiral https://api.spiral.ai/mcp
- Sign in
Start amp. Amp opens Spiral's sign-in page in your browser: sign in, pick the organization and click Authorize. No API key.
- Check it
amp mcp doctor
Use the Spiral skill
- Send Amp 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 package vulnerability lookup
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", "input": { "name": "<name>" } }'
Then paste one of the prompts above: Amp finds OSV.dev package vulnerability lookup on Spiral, shows the price and runs it.
OSV.dev package vulnerability lookup providers and prices
Spiral runs OSV.dev package vulnerability lookup through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Amp for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Include details | on or off | Add each record's full Markdown description ( |
Every API field of OSV.dev open source vulnerabilities · Query is on its tool page: open its card above.
What can you do with OSV.dev package vulnerability lookup in Amp?
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 package vulnerability lookup and Amp
Overview
OSV.dev package vulnerability lookup in other agents
Questions about OSV.dev package vulnerability lookup in Amp
Can Amp use OSV.dev package vulnerability lookup?
Yes. Add Spiral to Amp as an MCP server, and Amp can find and run OSV.dev package vulnerability lookup like any built-in tool.
How much does OSV.dev package vulnerability lookup cost in Amp?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Amp plan is separate.
Do I need an Alexandria account to use OSV.dev package vulnerability lookup in Amp?
No. Spiral runs OSV.dev package vulnerability lookup 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 package vulnerability lookup in Amp?
About two minutes: add the server, then sign in, then check it.
Does Amp wait while OSV.dev package vulnerability lookup runs?
OSV.dev package vulnerability lookup runs in the background. Amp 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 package vulnerability lookup in Amp
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Amp:
set up https://spiral.ai/SKILL.md


