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

opencode · Developer

How to Use CVE.org vulnerability record in opencode

Retrieve a known CVE's description, affected products and versions, references, and available enrichment. Use it to investigate one vulnerability and check the evidence behind an alert.

Prompts to try with CVE.org vulnerability record in opencode

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

Use CVE.org vulnerability record for CVE-2021-44228 and compare its affected products and versions with this repository's Maven dependency files. Write an evidence note with the record's references.

CVE.org vulnerability recordopencode
Try asking
  • Use CVE.org vulnerability record for CVE-2021-44228 and check whether our dependency matching code distinguishes log4j-core from other Apache Logging Services projects.

  • Use CVE.org vulnerability record to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from CVE.org vulnerability record and tell me what changed since last week.

  • Check CVE.org vulnerability record and summarize what you find in three bullet points.

How to set up CVE.org vulnerability record in opencode

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

Use Spiral's MCP server

  1. Add the server

    Leave out --global to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.

    opencode mcp add spiral --global --url https://api.spiral.ai/mcp
  2. Sign in

    Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, /mcps starts the same sign-in.

    opencode mcp auth spiral
  3. Check it

    Spiral shows as connected.

    opencode mcp list

Use the Spiral skill

  1. Send opencode 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 CVE.org vulnerability record

    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": "cve-org/vulnerabilities/cve_record",
        "input": {
          "cve_id": "<cve_id>"
        }
      }'

Then paste one of the prompts above: opencode finds CVE.org vulnerability record on Spiral, shows the price and runs it.

CVE.org vulnerability record providers and prices

Spiral runs CVE.org vulnerability record through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
CVE Program (CVE.org) CVE Services · Cve record
cve-org/vulnerabilities/cve_record

What can you do with CVE.org vulnerability record in opencode?

Build a review queue that connects CVE evidence to the project's dependencies. A coding agent can inspect affected products and versions, identify recent record changes, and resolve assigning organizations.

Prepare a daily vulnerability brief

Discover newly published and revised CVEs, investigate selected records, and identify the assigning organizations through the CNA directory.

Review supplier vulnerability evidence

Collect recent CVE changes relevant to Apache or another supplier, inspect affected products and references, and check the assigning CNA's scope.

Investigate advisory corrections

Use updated CVEs to build a review queue, examine their current records, and locate the CNA's public reporting instructions when a correction needs investigation.

Audit CVE assignment provenance

Sample recently changed CVEs, read their assignment metadata, and resolve CNA short names into organizations and scopes for an evidence report.

Review dependencies before a release

Compare affected products and versions in selected CVE records with a project's dependency inventory, using recent changes to find additional records worth checking.

Revisit existing vulnerability tickets

Match recently updated CVE identifiers against an existing ticket list, then retrieve current records to review affected versions and supporting references.

Questions about CVE.org vulnerability record in opencode

Can opencode use CVE.org vulnerability record?

Yes. Add Spiral to opencode as an MCP server, and opencode can find and run CVE.org vulnerability record like any built-in tool.

How much does CVE.org vulnerability record cost in opencode?

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

Do I need an Alexandria account to use CVE.org vulnerability record in opencode?

No. Spiral runs CVE.org vulnerability record on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up CVE.org vulnerability record in opencode?

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

Does opencode wait while CVE.org vulnerability record runs?

CVE.org vulnerability record runs in the background. opencode starts the run, checks on it and gives you the json when it's ready.

Does CVE include unpublished vulnerability details?

The CVE Program catalogs publicly disclosed vulnerabilities. An identifier marked RESERVED can exist before its vulnerability details are published.

How quickly does CVE.org information change?

The official CVE repository updates about every seven minutes. CNA organization information follows a different schedule: the organization guide says website updates occur on Tuesdays.

How much recent change history does the source retain?

The official repository's deltaLog.json normally keeps a rolling 30 days of record modification history. That window describes the change log, not the age of vulnerabilities in the CVE catalog.

What information identifies an affected vulnerability?

CVE JSON records include the CVE identifier, affected products and versions, and public references. Those references provide the supporting reports and advisories for further investigation.

How do I choose the right CNA for a product?

Choose a CNA whose published scope includes the affected product. CVE.org partner profiles provide reporting instructions, including disclosure policy and contact links.

Get started

Start using CVE.org vulnerability record in opencode

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

Paste this into opencode:

Set up opencode

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