Spiral gives your agent every tool with one account. Browse the tools →

dots · Developer

How to Use OSV.dev vulnerability details in dots

Fetch one vulnerability record by ID, with descriptions, affected packages, ranges, and references when supplied. Use it to investigate a finding or read the advisory behind a dependency check.

Prompts to try with OSV.dev vulnerability details in dots

Copy an example into dots, or ask in your own words.

Once a week, use OSV.dev vulnerability details for GHSA-jfh8-c2jp-5v3q. Report changes to affected packages, version ranges, descriptions, or withdrawal status.

OSV.dev vulnerability detailsdots
Try asking
  • Daily, use OSV.dev vulnerability details for GHSA-35jh-r3h4-6jhm. Summarize changes to its affected-package information and references.

  • Every Monday at 9am: use OSV.dev vulnerability details to look this up and give me the result as a table.

  • Pull the latest numbers from OSV.dev vulnerability details and tell me what changed since last week.

  • Check OSV.dev vulnerability details and summarize what you find in three bullet points.

How to set up OSV.dev vulnerability details in dots

Pick the way that suits you. Each takes about two minutes.

Use the Spiral skill

  1. Send dots this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. 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

  1. Create an API key

    In the console, open API keys and create a key for your dot. Copy it.

  2. Send your dot this message

    Your dot reads Spiral's skill and asks for your API key.

    set up https://spiral.ai/SKILL.md
  3. 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

  1. 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

  1. Create an API key

    In the console, under API keys.

  2. Run OSV.dev vulnerability details

    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/vuln",
        "input": {
          "id": "<id>"
        }
      }'

Then paste one of the prompts above: dots finds OSV.dev vulnerability details on Spiral, shows the price and runs it.

OSV.dev vulnerability details providers and prices

Spiral runs OSV.dev vulnerability details through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper

What can you do with OSV.dev vulnerability details 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.

Questions about OSV.dev vulnerability details in dots

Can dots use OSV.dev vulnerability details?

Yes. Add Spiral to dots as an MCP server, and dots can find and run OSV.dev vulnerability details like any built-in tool.

How much does OSV.dev vulnerability details 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 vulnerability details in dots?

You need no Alexandria account. dots uses one Spiral API key for every tool, and Spiral runs OSV.dev vulnerability details on its own Alexandria account.

How long does it take to set up OSV.dev vulnerability details 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 vulnerability details runs?

OSV.dev vulnerability details 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.

Get started

Start using OSV.dev vulnerability details in dots

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into dots:

Set up dots

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options