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

Gemini · Developer

How to Use OSV.dev dependency vulnerability check in Gemini

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 Gemini

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

Use OSV.dev dependency vulnerability check for npm lodash 4.17.15, PyPI jinja2 3.1.4, and Maven org.apache.logging.log4j:log4j-core 2.14.1. Show the vulnerability IDs found for each package.

OSV.dev dependency vulnerability checkGemini
Try asking
  • 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.

  • Pull the newest data from OSV.dev dependency vulnerability check and give me the result as a table.

How to set up OSV.dev dependency vulnerability check in Gemini

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

Use the Gemini connector

  1. Open Connected Apps

    On your computer, go to gemini.google.com. At the bottom, click Settings › Connected Apps. If you don't see Connected Apps, click Personal Intelligence first, then Connected Apps.

  2. Add Spiral as a custom app

    Under Custom apps, click Add a custom app and paste this MCP server URL:

    https://api.spiral.ai/mcp
  3. Sign in to Spiral and approve

    Follow the on-screen instructions. Spiral opens: sign in, pick the organization and click Authorize. No API key.

Use the Spiral skill

  1. Send Gemini 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 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 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: Gemini 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.

AlexandriaDeveloper
OSV.dev open source vulnerabilities · Query batch
osv-dev/vulnerabilities/query_batch

What can you do with OSV.dev dependency vulnerability check in Gemini?

Get a readable explanation of the known vulnerabilities attached to a package version or advisory ID. A chat app can organize OSV.dev findings by affected package and explain the descriptions and references supplied by the source.

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 dependency vulnerability check in Gemini

Can Gemini use OSV.dev dependency vulnerability check?

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

How much does OSV.dev dependency vulnerability check cost in Gemini?

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Gemini plan is separate.

Do I need an Alexandria account to use OSV.dev dependency vulnerability check in Gemini?

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 Gemini?

About two minutes: open Connected Apps, then add Spiral as a custom app, then sign in to Spiral and approve.

Does Gemini wait while OSV.dev dependency vulnerability check runs?

OSV.dev dependency vulnerability check runs in the background. Gemini 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 dependency vulnerability check in Gemini

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

Paste this into Gemini:

Set up Gemini

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