Give your coding agent the dependency graph it is about to change: scan, diff, explain, audit
io.github.bomly-dev/bomly-cli โ MCP Server for Dependency Graph Analysis
The Model Context Protocol (MCP) server io.github.bomly-dev/bomly-cli provides tooling for a coding agent to analyze a dependency graph. It focuses on scanning, diffing, explaining, and auditing dependencies, with emphasis on security artifacts and compliance workflows.
๐ ๏ธ Key Features
Dependency graph analysis
Scan, diff, explain, and audit capabilities
Security and compliance-oriented outputs
๐ Use Cases
License compliance checks
Supply-chain security auditing
Vulnerability auditing and dependency analysis
SBOM management (software-bill-of-materials)
โก Developer Benefits
Supports SBOM and standards-related ecosystems (CycloneDX, SPDX)
Integrations and formats referenced include OSV, SARIF, and SBOM/SCA workflows
Designed for CI/CD contexts, including GitHub Actions
Bomly is a free, open-source command-line tool for understanding what your software depends on. It is built for developers, security engineers, and CI pipelines. Bomly:
scans source trees, SBOMs, Git refs, and container images into one dependency graph;
explains why a package is present;
adds vulnerability and license data when you ask for it with --enrich;
checks the result against your policy and exits with a code CI can act on;
writes JSON, SARIF, SPDX, and CycloneDX output.
No account, no login, no service to host, no telemetry. One binary. Bomly contacts no vulnerability or license service unless you pass --enrich. Network and privacy lists every network trigger so you can check that claim yourself.
Install
bash
# macOS / Linuxbrew
brew install bomly-dev/tap/bomly
# Linux / macOS install script
curl -fsSL https://bomly.dev/install.sh | sh
# Windows
winget install Bomly.BomlyCLI
Check the install with bomly version. Installation covers Linux packages, Scoop, go install, the smaller bomly-lite binary that uses your own Syft and Grype, checksums, and uninstalling.
Start with a scan
bash
# Scan the current project
bomly scan
# Scan a specific directory
bomly scan --path ./services/api
# Scan a container image
bomly scan --image ghcr.io/example/app:latest
# Scan a remote Git ref
bomly scan --url https://github.com/owner/repo --ref v1.2.3
# Read an existing SPDX or CycloneDX SBOM
bomly scan --sbom --path ./sbom.cdx.json
Bomly reads manifests, lockfiles, package-manager output, container layers, or existing SBOMs and turns them into one dependency graph. Native detectors cover Go, npm, pnpm, Yarn, Maven, Gradle, Python, Composer, Bundler, GitHub Actions, and more. Syft covers the remaining ecosystems and container images. See the Support matrix and Scan targets.
Reachability is experimental: "unreachable" is not a guarantee of safety. Use cases has more recipes, and Release assurance lists the checks every release goes through.
Explore interactively
Open the terminal UI when you want to inspect a graph by hand:
bash
bomly scan --interactive
Use it to fuzzy-find packages, inspect versions and scopes, pivot through findings, and see how a dependency entered the graph without writing a report to disk. See Interactive TUI.
Gate pull requests
The Bomly Guard action runs bomly diff against a pull request's merge base and posts the result as a check and a PR comment. Only the packages the PR changed are audited, so existing findings elsewhere never block a PR:
Bomly can run as a local server for the Model Context Protocol (MCP), so an AI coding agent can call the same scan, explain, and diff tools you use on the command line:
bash
bomly mcp serve
If you have not installed the CLI, the bomly-mcp npm wrapper starts the same server:
bash
npx -y bomly-mcp
See MCP server for the Claude Code, Cursor, and VS Code setup and the tool reference.
Configure and extend
Bomly reads settings from ~/.bomly/config.yaml, then from the file named by --config or BOMLY_CONFIG, then from BOMLY_* environment variables, then from flags. Later sources win. A config file inside a repository is never loaded on its own: pass --config .bomly/config.yaml to use one. See the Config reference.
Plugins add detectors, matchers, auditors, and analyzers without forking Bomly: