Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.115.4 instead.
Reason given by maintainers: Security fixes; upgrade to 0.114.0 or later

agent-bom

AI supply-chain BOM: every agent, MCP server and AI package, and what each one can reach.

For AppSec teams and developers who run Claude Code, Cursor, Codex or any MCP client: see which agents, MCP servers, tools and packages are installed, which are vulnerable, and what each one can reach. Local scans need no account. Try it in your browser first, no install.

With uv installed, run from the repository you want to inspect:

uvx agent-bom scan . --no-discover -f html -o agent-bom-report.html

Open agent-bom-report.html for inventory, findings and fix guidance. Run the same scan again later and agent-bom prints what changed since the last one. No MCP configuration? Package findings still apply. Incomplete evidence is not a clean result: what a scan does and does not establish. For a bundled sample, run uvx agent-bom scan --demo --offline; status 1 is the expected security verdict for its blocking findings.

agent-bom demo

Where Start with You get
On your laptop uvx agent-bom scan . and claude mcp add agent-bom -- uvx agent-bom mcp server Findings with fixes, a delta on every rescan, agent-bom as a tool in your coding agent
In your team uses: koda-ai-studio/agent-bom@v0 on pull requests plus a weekly schedule: A PR gate with a findings comment and SARIF, and a weekly rescan for new CVEs
Across your org agent-bom up, then Docker Compose or the Helm chart Retained scans, one graph of agents, servers, packages and credentials, SSO and audit in your infrastructure

Credential references are names, not secret values. Recorded relationships do not prove exploitation or successful data access.

For the installed-command examples below, run pip install agent-bom in a virtual environment. If you want an inspectable sample before scanning your own repo:

agent-bom samples first-run
agent-bom scan --inventory agent-bom-first-run/inventory.json -p agent-bom-first-run --enrich

The bundled first-run stack includes agent inventory, MCP server definitions, placeholder credential environment variable names, Python/npm manifests, and a prompt file. See docs/FIRST_RUN.md in the repository for the guided flow.

Follow one component

In the self-hosted dashboard, open Inventory → component → Findings → Compliance. The views retain the exact component and scan snapshot, expose recorded relationships and source evidence, and export loaded evidence with completeness receipts. Control mappings do not establish evaluated passes or certification.

From a source checkout, run the connected-BOM example. It retains before/after SQLite snapshots: a changed dependency input removes one pinned advisory finding while an unrelated synthetic cloud check remains failed. This bounded example does not change a deployment or qualify a cloud account.

pip install agent-bom

agent-bom scan .                                 # Repo + MCP + package blast radius
agent-bom quickstart --dry-run --offline          # Sample-data and API/UI next steps
agent-bom samples first-run                      # Inspectable sample AI stack
agent-bom check flask@2.2.0 --ecosystem pypi     # Pre-install package verdict
agent-bom image nginx:latest                     # Container image scan
agent-bom scan . --remediate remediation.md       # Fix-first remediation plan
pip install 'agent-bom[ui]'                      # once, if you want the dashboard
agent-bom serve --persist ~/.agent-bom/control-plane.db  # restart-safe local control plane

The base wheel is the scanner/CLI path and includes MCP server mode (agent-bom mcp server). Install optional surfaces explicitly: pip install 'agent-bom[ui]' for the local API/dashboard process. Use pip install 'agent-bom[all]' for supported first-run extras; MLflow remains separate until its upstream CVE backlog is fixed. If an extra is missing, the command exits with the matching install hint.

Self-hosted pilot:

curl -fsSL https://raw.githubusercontent.com/koda-ai-studio/agent-bom/main/deploy/docker-compose.pilot.yml -o docker-compose.pilot.yml
docker compose -f docker-compose.pilot.yml up -d
# Dashboard -> http://localhost:3000

For production, configure the database, identity and ingress settings in a release checkout. Follow the required secret bootstrap and wait for all four target Secrets before installing the workload:

helm upgrade --install agent-bom oci://ghcr.io/koda-ai-studio/charts/agent-bom --version 0.113.0 \
  --namespace agent-bom --create-namespace \
  -f deploy/helm/agent-bom/examples/eks-production-values.yaml

Product views

Dashboard

agent-bom dashboard overview

Follow an agent to its findings

Sample production environment showing agents, MCP servers, dependencies and findings, with modeled access labeled

Follow Document Intake Agent → document-tools MCP → pillow@9.0.0 → CVE-2023-4863. This is a fictional sample estate; dashed access and credential links are modeled, not observed execution.

Inspect why two records are linked

Repository pin, image inventory and deployment occurrence resolve to one package, with relationship evidence open

Real parsers, modeled local infrastructure: a repository pin, image SBOM and Kubernetes workload resolve to one package. The image inventory and deployment occurrence stay distinct. Select an arrow to inspect its source and evidence; a graph path does not prove execution or exploitation.

Explore the reference evidence lab · Graph guide

What it scans

  • Agents + MCP — MCP clients, servers, tools, transports, trust posture
  • Skills + instructions — CLAUDE.md, AGENTS.md, .cursorrules, .windsurfrules, skills/*
  • Package risk — supply-chain scanning across 15 package ecosystems (including mix.lock / pubspec.lock for Hex and Pub) with OSV/GHSA enrichment and blast radius
  • AI models + datasets — malicious-model detection via safe pickle-opcode disassembly (no execution), model/dataset cards, and target-scoped PII/PHI dataset-file scanning
  • Container images + IaC — native OCI parsing plus Dockerfile, Terraform, CloudFormation, Helm, and Kubernetes coverage
  • Cloud estate — read-only, gated asset inventory across AWS/Azure/GCP plus AI/GPU posture and CIS benchmarks
  • Identity (NHI) — non-human identity discovery (Okta/Entra), credential-expiry posture, and access-review campaigns
  • LLM cost — spend forecasting, budget runway, chargeback/allocation, and seasonal-aware spend-anomaly detection
  • Secrets + runtime — MCP proxy/gateway, inline firewall enforcement, A2A/MCP auth posture, Shield SDK, secrets, and redaction surfaces
  • Compliance + evidence — mapped governance plus ZIP evidence bundles for auditors

Supported sources

Discovery and scanning read from these sources today; the last row lists where evidence can be sent. The list is generated from a code-backed manifest (docs/images/integrations-manifest.json); a test fails if it names anything without an implementation.

Area Integrations
AI clients + IDEs Claude, Codex, Cursor, GitHub Copilot, Windsurf, Cortex Code, Gemini CLI, JetBrains AI, Junie, Amazon Q, Cline, Roo Code, Continue, Zed, Goose, Snowflake CLI, Docker MCP Toolkit, Tabnine, Sourcegraph Cody, Aider, Void, Aide, Trae, Pieces, OpenClaw, mcp-cli
AI platforms + model hubs OpenAI, Hugging Face, Ollama, MLflow, W&B, Langfuse, LangSmith
GPU + neo clouds CoreWeave, Nebius, Lambda, RunPod, Vast.ai, Crusoe, GPU containers + K8s GPU nodes
Hyperscalers + Kubernetes AWS, Azure, GCP, Kubernetes
Data + vector stores Snowflake, Databricks, Supabase, Pinecone, Qdrant, Weaviate, Chroma, Milvus
Identity + SaaS + dev Okta, GitHub Actions, Vercel, Microsoft Entra ID, Jira, ServiceNow, Slack, Jamf
Evidence out ClickHouse, BigQuery, S3, GCS, Azure Blob, Jira tickets, Slack alerts, Vanta, Drata, OCSF syslog

Product names and logos are trademarks of their owners, used only to identify supported evidence sources. Their use does not imply endorsement or partnership.

Key features

  • Blast radius + attack-path fusion — multi-hop exposure paths over one UnifiedGraph, from package → finding → MCP server → credentials → connected agents
  • CWE-aware impact — RCE shows credential exposure, DoS does not; symbol-level CVE reachability joins CWE/CVE/CPE advisory context when OSV/GHSA carry affected symbols (Python, npm, Go)
  • Portable outputs — SARIF, CycloneDX, SPDX, OCSF, HTML, graph, JSON, ZIP evidence bundles, and more
  • MCP server mode — start with 8 scan-profile tools; use agent-bom mcp server --profile full for the complete catalog of 99 MCP tools, 7 resources, and 8 workflow prompts in Claude, Cursor, Windsurf, and Cortex CoCo / Cortex Code
  • Skill bundle identity — stable bundle hashes for skill and instruction file review
  • Dependency confusion detection — flags internal naming patterns
  • VEX generation — auto-triage with CWE/CVE/CPE-aware reachability (package + function-level when advisory symbols exist)

Discovery and static/cloud scanning are read-only by default. Explicit disk side-scans create temporary cloud resources and need additional permissions. Proxy, gateway, Shield, and control-plane write tools are separate, explicit runtime or authenticated operations. See the permission and network boundaries before enabling cloud scans or outbound integrations.

How the data moves

How agent-bom works

Blast radius

Blast radius

Metadata

Release files for agent-bom 0.113.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-bom 0.113.1
File Size Uploaded Provenance Actions
agent_bom-0.113.1.tar.gz 12.8 MB With provenance Details for agent_bom-0.113.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for agent-bom 0.113.1
File Interpreter ABI Platform Actions
agent_bom-0.113.1-py3-none-any.whl Python 3 none any Details for agent_bom-0.113.1-py3-none-any.whl

Total release size: 23.1 MB

Release files / agent_bom-0.113.1.tar.gz

Download URL agent_bom-0.113.1.tar.gz
Size 12.8 MB
Tags Source
SHA-256 checksum
How to use checksums
e27e79cbfd73590e56cdaaa5667cc9988b82e5375d6d9f1ae8a269072b920589
BLAKE2b-256 checksum
How to use checksums
66113468e2df4cf34a7a6650548010c10f483d7f8fba0aca88e52e6408eb3134
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

Release files / agent_bom-0.113.1-py3-none-any.whl

Download URL agent_bom-0.113.1-py3-none-any.whl
Size 10.3 MB
Tags Python 3
SHA-256 checksum
How to use checksums
45a8f114d2172cf810ec28de10a66d4d7d823deaeb7b40f482343ae393cf1b92
BLAKE2b-256 checksum
How to use checksums
501fa80b815a4ed4a9a6289b51147fdc0b1d9bc782b691172cdfd2ba313561b5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

Security for agent-bom 0.113.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for agent_bom-0.113.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.113.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page