[Integrations](https://spiral.ai/integrations) › [Grok](https://spiral.ai/integrations/grok) › [OSV.dev package vulnerability lookup](https://spiral.ai/integrations/grok/osv-dev-package-vulnerability-lookup)

# How to Use OSV.dev package vulnerability lookup in Grok

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.

|  |  |
| --- | --- |
| Model | OSV.dev package vulnerability lookup |
| 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 package vulnerability lookup in Grok

- Use OSV.dev package vulnerability lookup for npm lodash version 4.17.15. List the matching advisories and summarize any affected ranges returned.
- Use OSV.dev package vulnerability lookup to compare npm lodash versions 4.17.15 and 4.17.21. Show which advisory IDs appear for each version.
- Use OSV.dev package vulnerability lookup to look this up and give me the result as a table.
- 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 Grok

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

### Use the Grok connector

1. **Add a custom connector**: In Grok open Settings › Connect Apps, then Add a custom connector. Name it Spiral, paste this URL, leave Headers empty and click Add MCP.

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Grok opens Spiral: sign in, pick the organization and click Authorize. Spiral gives the connection its own API key; Grok never sees it, and you can remove the connection under Settings › Connected apps.

3. **Check that it is connected**: Connect Apps › Custom shows Spiral as Connected. It works in every Grok chat and Grok bot.

### Use the Spiral skill

1. **Send Grok 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 package vulnerability lookup**: 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",
    "input": {
      "name": "<name>"
    }
  }'
```

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

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

## OSV.dev package vulnerability lookup tools and prices

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

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| name |  | — | Package name in the ecosystem: `lodash`, `jinja2`, `golang.org/x/net`, `org.apache.logging.log4j:log4j-core` (Maven group:artifact). |
| purl |  | — | Package URL instead of ecosystem+name, optionally with the version: pkg:npm/lodash@4.17.15, pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1. |
| commit |  | — | Full Git commit hash: vulnerabilities whose affected ranges include it (C/C++ and other source-level records). Pattern: ^[0-9a-fA-F]{40}$. |
| cursor |  | — | next_cursor from a previous answer for the same query (OSV.dev page token). |
| version |  | — | Exact version to check (4.17.15). Omit to list every vulnerability recorded for the package. |
| ecosystem |  | — | OSV ecosystem: npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, Packagist, Pub, Hex, Hackage, CRAN, GitHub Actions, or a distribution with release (Debian:12, Alpine:v3.20, Ubuntu:22.04:LTS). Case-insensitive; cargo, golang, gem and composer are accepted. Use with `name`. |

## What can you do with OSV.dev package vulnerability lookup in Grok?

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.

## Overview

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

## OSV.dev package vulnerability lookup in other agents

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

## More Grok guides

- [OSV.dev dependency vulnerability check](https://spiral.ai/integrations/grok/osv-dev-dependency-vulnerability-check)
- [OSV.dev vulnerability details](https://spiral.ai/integrations/grok/osv-dev-vulnerability-details)
- [Notion template listings](https://spiral.ai/integrations/grok/notion-template-listings)
- [Ollama model details](https://spiral.ai/integrations/grok/ollama-model-details)
- [Notion template details](https://spiral.ai/integrations/grok/notion-template-details)
- [Ollama model layer metadata](https://spiral.ai/integrations/grok/ollama-model-layer-metadata)

## Questions about OSV.dev package vulnerability lookup in Grok

**Can Grok use OSV.dev package vulnerability lookup?**

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

**How much does OSV.dev package vulnerability lookup cost in Grok?**

$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 plan is separate.

**Do I need an Alexandria account to use OSV.dev package vulnerability lookup in Grok?**

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

About two minutes: add a custom connector, then sign in to Spiral and approve, then check that it is connected.

**Does Grok wait while OSV.dev package vulnerability lookup runs?**

OSV.dev package vulnerability lookup runs in the background. Grok 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.

