Zurück zu den Updates
New releaseJul 25, 2026

agent-bom v0.98.0

Offener Sicherheitsscanner und selbstgehostete Steuerungsebene für KI, MCP und Cloud. Ein einheitliches Beweismodell — führen Sie Scans in Ihrer Umgebung durch, zentralisieren Sie Ergebnisse und verwalten Sie sie in Ihrer VPC.

Teilen

agent-bom — Discover. Scan. Correlate. Act. Security evidence across repositories, software supply chains, AI and MCP, cloud, identity, and data.

Build PyPI Python 3.11 through 3.14 Docker pulls

Apache-2.0 license OpenSSF Scorecard Glama MCP server Smithery MCP server

Find vulnerable software behind your AI agents—and trace the exposure evidence.

Open security scanner and self-hosted control plane for AI, MCP, and cloud infrastructure. For AppSec and platform engineers: scan a repository, trace findings through agents and infrastructure, and prioritize fixes using blast radius and reachability evidence. Local scans need no account.

Quick start · Integrations · Sample graph · Self-host · Product tour · Docs

Quick start

From the repository you want to inspect, with uv installed:

uvx agent-bom scan .

Read the discovered agents and MCP servers, prioritize the highest-severity findings, and follow the affected package's fix guidance. Review coverage gaps beside the verdict: incomplete evidence is not a clean assessment. What this scan does and does not establish.

No project handy? Run uvx agent-bom scan --demo --offline for a bundled sample. Exit 1 is expected: the sample trips the security gate. A non-zero exit can mean a security gate or incomplete assessment; inspect the report and coverage. See the exit codes.

Verify fixes, export reports, and add a CI gate

Apply a reviewed fix, update the lockfile, then rerun uvx agent-bom scan . against the same repository to verify the finding changed. Save a report with uvx agent-bom scan . -f sarif -o findings.sarif, then upload it and gate CI. Run uvx agent-bom doctor if setup fails. See the first-run guide for pip installation, or ask your coding agent with the checkup skill.

In GitHub Actions, the same scan uploads SARIF to code scanning and fails on high or critical findings, the same default gate as the CLI:

permissions:
  contents: read
  security-events: write
steps:
  - uses: actions/checkout@v4
  - uses: koda-ai-studio/agent-bom@v0
    with:
      upload-sarif: 'true'

Recorded agent-bom CLI showing sample findings and remediation guidance; no fix executed

The recording uses labeled sample data and bundled advisories. Credential references are names, not secret values. Recorded relationships do not prove exploitation or successful data access.

What it covers

AreaWhat you get
DependenciesLockfiles and manifests across Python, JavaScript, Go, Java, .NET, Rust and more, matched against OSV, GitHub advisories and NVD with KEV and EPSS. Ask "am I affected by CVE-X" across every stored scan.
CodeFindings from Semgrep or any SARIF tool, plus native analysis of AI code (prompt-injection sinks, guardrails, tool exposure) and whether your code reaches the vulnerable function.
Containers and IaCImages scanned in bounded memory and time; Dockerfile, Terraform, Kubernetes, Helm and compose risks with exact lines in SARIF.
AI agents and MCPAgents, MCP servers, tools and credentials from local configs and agent frameworks, linked to what they can reach.
CloudRead-only collection from AWS, Azure, GCP, Databricks, Snowflake and more, with CIS and best-practice checks in the same graph.
RuntimeAn MCP proxy and gateway that alert on poisoned tools and injected results, or block them with --injection-mode enforce.
All supported sources and evidence destinations

Discovery and scanning read from these sources; the last row lists evidence destinations.

AreaIntegrations
AI clients + IDEsClaude, 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 hubsOpenAI, Hugging Face, Ollama, MLflow, W&B, Langfuse, LangSmith
GPU + neo cloudsCoreWeave, Nebius, Lambda, RunPod, Vast.ai, Crusoe, GPU containers + K8s GPU nodes
Hyperscalers + KubernetesAWS, Azure, GCP, Kubernetes
Data + vector storesSnowflake, Databricks, Supabase, Pinecone, Qdrant, Weaviate, Chroma, Milvus
Identity + SaaS + devOkta, GitHub Actions, Vercel, Microsoft Entra ID, Jira, ServiceNow, Slack, Jamf
Evidence outClickHouse, 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.

Investigate context and exposure

Kategorien