How to Use OSV.dev dependency vulnerability check in dots
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 dots
Copy an example into dots, or ask in your own words.
Every morning, use OSV.dev dependency vulnerability check for npm lodash 4.17.15 and PyPI jinja2 3.1.4. Report newly returned vulnerability IDs and changes to their modification times.
Every Monday, use OSV.dev dependency vulnerability check for npm lodash 4.17.15 and 4.17.21. Compare the advisory IDs returned for the two versions and report changes since last week.
Every Monday at 9am: use OSV.dev dependency vulnerability check to look this up and give me the result as a table.
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 dots
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send dots 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 Spiral's MCP server
- Create an API key
In the console, open API keys and create a key for your dot. Copy it.
- Send your dot this message
Your dot reads Spiral's skill and asks for your API key.
set up https://spiral.ai/SKILL.md
- Give your dot the key
When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.
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: dots 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 dots?
Keep a dependency review queue current as OSV.dev publishes new or revised findings. A scheduled agent can repeat package checks, compare returned IDs and modification times, and summarize advisory changes for review.
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 dots
Overview
OSV.dev dependency vulnerability check in other agents
Questions about OSV.dev dependency vulnerability check in dots
Can dots use OSV.dev dependency vulnerability check?
Yes. Add Spiral to dots as an MCP server, and dots can find and run OSV.dev dependency vulnerability check like any built-in tool.
How much does OSV.dev dependency vulnerability check cost in dots?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.
Do I need an Alexandria account to use OSV.dev dependency vulnerability check in dots?
You need no Alexandria account. dots uses one Spiral API key for every tool, and Spiral runs OSV.dev dependency vulnerability check on its own Alexandria account.
How long does it take to set up OSV.dev dependency vulnerability check in dots?
About two minutes: create an API key, then send your dot this message, then give your dot the key.
Does dots wait while OSV.dev dependency vulnerability check runs?
OSV.dev dependency vulnerability check runs in the background. dots 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 dots
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into dots:
set up https://spiral.ai/SKILL.md


