[Integrations](https://spiral.ai/integrations) › [Grok Build](https://spiral.ai/integrations/grok-build) › [OSV.dev dependency vulnerability check](https://spiral.ai/integrations/grok-build/osv-dev-dependency-vulnerability-check)

# How to Use OSV.dev dependency vulnerability check in Grok Build

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.

|  |  |
| --- | --- |
| Model | OSV.dev dependency vulnerability check |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with OSV.dev dependency vulnerability check in Grok Build

- 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 Grok Build

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

### Use Spiral's MCP server

1. **Add the server**: Add `--scope project` to add Spiral to the current repository only. No header and no client ID or secret: Grok registers itself with Spiral.

```bash
grok mcp add --transport http spiral https://api.spiral.ai/mcp
```

2. **Sign in**: Start `grok` and run `/mcps`. Select Spiral and press `i`. Your browser opens: sign in to Spiral, pick the organization and click Authorize. No API key.

3. **Check it**

```bash
grok mcp doctor spiral
```

### Use the Spiral skill

1. **Send Grok Build 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.

```bash
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.

```bash
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: Grok Build finds OSV.dev dependency vulnerability check on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/grok-build

## OSV.dev dependency vulnerability check tools and prices

- [OSV.dev open source vulnerabilities · Query batch](https://spiral.ai/tools/alexandria/osv-dev/vulnerabilities/query_batch) (Alexandria): $0.00873 per call.

## What can you do with OSV.dev dependency vulnerability check in Grok Build?

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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Grok Build guides](https://spiral.ai/integrations/grok-build)

## OSV.dev dependency vulnerability check in other agents

- [Amp](https://spiral.ai/integrations/amp/osv-dev-dependency-vulnerability-check)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/osv-dev-dependency-vulnerability-check)
- [Claude](https://spiral.ai/integrations/claude-desktop/osv-dev-dependency-vulnerability-check)
- [Claude Code](https://spiral.ai/integrations/claude-code/osv-dev-dependency-vulnerability-check)
- [Cline](https://spiral.ai/integrations/cline/osv-dev-dependency-vulnerability-check)
- [Codex](https://spiral.ai/integrations/codex/osv-dev-dependency-vulnerability-check)
- [Cursor](https://spiral.ai/integrations/cursor/osv-dev-dependency-vulnerability-check)
- [Devin](https://spiral.ai/integrations/devin/osv-dev-dependency-vulnerability-check)
- [dots](https://spiral.ai/integrations/dots/osv-dev-dependency-vulnerability-check)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/osv-dev-dependency-vulnerability-check)
- [Gemini](https://spiral.ai/integrations/gemini/osv-dev-dependency-vulnerability-check)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/osv-dev-dependency-vulnerability-check)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/osv-dev-dependency-vulnerability-check)
- [goose](https://spiral.ai/integrations/goose/osv-dev-dependency-vulnerability-check)
- [Grok](https://spiral.ai/integrations/grok/osv-dev-dependency-vulnerability-check)
- [Hermes](https://spiral.ai/integrations/hermes/osv-dev-dependency-vulnerability-check)
- [Instinct](https://spiral.ai/integrations/instinct/osv-dev-dependency-vulnerability-check)
- [Manus](https://spiral.ai/integrations/manus/osv-dev-dependency-vulnerability-check)
- [Muse](https://spiral.ai/integrations/muse/osv-dev-dependency-vulnerability-check)
- [Muse Code](https://spiral.ai/integrations/muse-code/osv-dev-dependency-vulnerability-check)
- [n8n](https://spiral.ai/integrations/n8n/osv-dev-dependency-vulnerability-check)
- [Notion](https://spiral.ai/integrations/notion/osv-dev-dependency-vulnerability-check)
- [OpenClaw](https://spiral.ai/integrations/openclaw/osv-dev-dependency-vulnerability-check)
- [opencode](https://spiral.ai/integrations/opencode/osv-dev-dependency-vulnerability-check)
- [Perplexity](https://spiral.ai/integrations/perplexity/osv-dev-dependency-vulnerability-check)
- [Raycast](https://spiral.ai/integrations/raycast/osv-dev-dependency-vulnerability-check)
- [VS Code](https://spiral.ai/integrations/vscode/osv-dev-dependency-vulnerability-check)
- [Windsurf](https://spiral.ai/integrations/windsurf/osv-dev-dependency-vulnerability-check)
- [Zapier](https://spiral.ai/integrations/zapier/osv-dev-dependency-vulnerability-check)

## More Grok Build guides

- [Notion template listings](https://spiral.ai/integrations/grok-build/notion-template-listings)
- [OSV.dev package vulnerability lookup](https://spiral.ai/integrations/grok-build/osv-dev-package-vulnerability-lookup)
- [Notion template details](https://spiral.ai/integrations/grok-build/notion-template-details)
- [OSV.dev vulnerability details](https://spiral.ai/integrations/grok-build/osv-dev-vulnerability-details)
- [Notion product release notes](https://spiral.ai/integrations/grok-build/notion-product-release-notes)
- [Ollama model details](https://spiral.ai/integrations/grok-build/ollama-model-details)

## Questions about OSV.dev dependency vulnerability check in Grok Build

**Can Grok Build use OSV.dev dependency vulnerability check?**

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

**How much does OSV.dev dependency vulnerability check cost in Grok Build?**

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

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

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 Grok Build?**

About two minutes: add the server, then sign in, then check it.

**Does Grok Build wait while OSV.dev dependency vulnerability check runs?**

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

