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

Codex · Developer

How to Use Docker Hub image vulnerability summary in Codex

Returns Docker Scout vulnerability counts for image digests. Use it to compare reported severity counts for candidate images after resolving their tags to digests.

Prompts to try with Docker Hub image vulnerability summary in Codex

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

Use Docker Hub image vulnerability summary for the library/nginx digests already recorded in our image review notes. Add the reported severity counts beside each digest.

Docker Hub image vulnerability summaryCodex
Try asking
  • Use Docker Hub image vulnerability summary to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from Docker Hub image vulnerability summary and tell me what changed since last week.

  • Check Docker Hub image vulnerability summary and summarize what you find in three bullet points.

  • Pull the newest data from Docker Hub image vulnerability summary and give me the result as a table.

How to set up Docker Hub image vulnerability summary in Codex

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

Use Spiral's MCP server

  1. Add the hosted server
    codex mcp add spiral --url https://api.spiral.ai/mcp
  2. Sign in

    Codex opens the browser: sign in to Spiral and click Authorize. No API key. codex mcp list then shows Spiral.

    codex mcp login spiral

Use the Spiral skill

  1. Send Codex 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 Docker Hub image vulnerability summary

    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": "hub-docker-com/container-images/get_image_vulnerability_summary",
        "input": {
          "digests": [
            "<digests>"
          ],
          "repository": "<repository>"
        }
      }'

Then paste one of the prompts above: Codex finds Docker Hub image vulnerability summary on Spiral, shows the price and runs it.

Docker Hub image vulnerability summary providers and prices

Spiral runs Docker Hub image vulnerability summary through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
Docker Hub · Get image vulnerability summary
hub-docker-com/container-images/get_image_vulnerability_summary

What can you do with Docker Hub image vulnerability summary in Codex?

Prepare an image change proposal with Docker Hub evidence beside the project's container references. A coding agent can turn repository documentation, publisher context, catalog categories, tags, and reported vulnerabilities into review notes.

Shortlist a base image

Use catalog categories to frame the search, find Python image candidates, and read their repository documentation. Compare Docker Scout severity counts for the candidate digests before choosing which images to test.

Plan an ARM migration

Find nginx image candidates and compare their tags for the target platform. Resolve shortlisted tags to platform digests, then compare the reported vulnerabilities for those exact images.

Prepare an image review record

For grafana/grafana, assemble the publisher profile, repository documentation, selected tag's platform digests, and reported vulnerability counts. Give reviewers the publisher context and exact image references behind a proposed deployment.

Assess an image upgrade

Read the nginx repository documentation and compare available tags. Inspect candidate tags for platform digests and sizes, then compare Docker Scout severity counts before preparing an upgrade proposal.

Questions about Docker Hub image vulnerability summary in Codex

Can Codex use Docker Hub image vulnerability summary?

Yes. Add Spiral to Codex as an MCP server, and Codex can find and run Docker Hub image vulnerability summary like any built-in tool.

How much does Docker Hub image vulnerability summary cost in Codex?

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

Do I need an Alexandria account to use Docker Hub image vulnerability summary in Codex?

No. Spiral runs Docker Hub image vulnerability summary on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up Docker Hub image vulnerability summary in Codex?

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

Does Codex wait while Docker Hub image vulnerability summary runs?

Docker Hub image vulnerability summary runs in the background. Codex starts the run, checks on it and gives you the json when it's ready.

Does public Docker Hub data include private repositories?

Public repositories are accessible to everyone. Private repositories require appropriate permissions, so a public publisher catalog does not establish everything that publisher stores.

Does one response contain every repository or tag?

Repository and tag listings are paginated. Docker Hub provides a total result count and a link to the next page when more results exist.

Can the same Docker Hub tag point to a different image later?

Yes. Docker Hub tags are mutable by default, and a publisher can change which image a tag references.

Can vulnerability counts change without another image push?

Yes. Docker Scout reevaluates stored image metadata as new vulnerability data becomes available, so an unchanged image can receive different findings.

Why can Docker Scout severity ratings differ from another scanner?

Scout prioritizes severity data from the vendor matching the package and version, such as Debian data for Debian packages. It falls back to NIST scoring when the vendor does not provide scoring data.

Get started

Start using Docker Hub image vulnerability summary in Codex

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

Paste this into Codex:

Set up Codex

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