Bomly

io.github.bomly-dev由 GitHub 账号 bomly-dev 发布v0.30.1更新于 Oct 30, 2026

Give your coding agent the dependency graph it is about to change: scan, diff, explain, audit

已验证STDIO仅桌面开发者工具安全与监控

概览

AI 生成的概览

Bomly 把依赖图命令行工具开放给编码助手:扫描项目的依赖与漏洞、比较两个目标的差异,并解释某个包为何存在。

可以做什么
  • 扫描项目、目录、容器镜像、Git 引用或已有 SBOM,生成依赖图,可选补充漏洞与许可证数据及策略审计结果
  • 比较两个目标之间的依赖变化,列出新增、消除和持续存在的发现及修复建议
  • 解释某个包为何存在并展示其依赖路径,可选附带漏洞详情与策略结果
  • 列出可用的插件(检测器、匹配器、审计器)及其启用或禁用状态
适用场景
适合在助手即将改动依赖时先看清依赖图、检查已知漏洞与修复方案,或审阅某个分支、拉取请求带来的变化。也适合在删除或升级某个包之前弄清它为何出现在依赖树中。
运行要求
以本地 stdio 进程运行,可通过已安装的 Bomly 命令行或使用 npx 启动的 bomly-mcp npm 包装器;使用包装器需要 Node.js。无需账号、登录或 API 密钥。仅在请求补充数据时才会访问网络。
安装前请注意
启用补充数据选项会联系外部漏洞与许可证服务,从而把包信息发送到本机之外;不启用时保持离线。扫描可读取容器镜像和远程 Git 引用,插件列表反映本机已安装的插件,使用前应确认已安装插件的可信度。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Bomly,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Bomly CLI]

Analyze Your Software DNA.

[CI] [OpenSSF Scorecard] [Latest release] [GitHub release downloads] [License: Apache-2.0] [Go Reference]

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 / Linuxbrewbrew install bomly-dev/tap/bomly
# Linux / macOS install scriptcurl -fsSL https://bomly.dev/install.sh | sh
# Windowswinget 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 projectbomly scan
# Scan a specific directorybomly scan --path ./services/api
# Scan a container imagebomly scan --image ghcr.io/example/app:latest
# Scan a remote Git refbomly scan --url https://github.com/owner/repo --ref v1.2.3
# Read an existing SPDX or CycloneDX SBOMbomly 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.

[Bomly scan progress showing indexed subprojects, detected dependencies, enriched packages, and resolved graph]

What Bomly can answer

QuestionCommandRead more
What do we depend on?bomly scanGetting started
Which packages have known vulnerabilities, and is there a fix?bomly scan --enrichMatchers
Should this build fail?bomly scan --enrich --audit --fail-on highAuditors, Exit codes
Which findings can my code reach? (experimental)bomly scan --enrich --audit --analyze --fail-on high --fail-on reachableReachability
Why is this package here?bomly explain lodashexplain
What changed in this PR?bomly diff --base main --head HEAD --enrich --auditdiff
Give me an SBOMbomly scan -o spdx=sbom.spdx.json -o cyclonedx=sbom.cdx.jsonSBOM formats
Give me something CI can readbomly scan --json, --format sarifOutput formats

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.

[Bomly interactive TUI overview with component, vulnerability, license, target, and distribution panels]

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:

yaml
# .github/workflows/bomly.yml- uses: actions/checkout@v5  with:    fetch-depth: 0- uses: bomly-dev/bomly-guard@v1  with:    fail-on: high

See Bomly Guard. CI integration has recipes for GitLab, Jenkins, Azure DevOps, and CircleCI.

[GitHub pull request checks showing Bomly Guard failing a required dependency check]

Use Bomly with AI agents

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:

bash
bomly plugins install github:bomly-dev/[email protected]bomly plugins enable bomly.examples.detector.bun-lockbomly plugins verify bomly.examples.detector.bun-lock

See Plugins to install and trust plugins, and Plugin authoring to write one.

Documentation

Contributor setup lives in CONTRIBUTING.md. Architecture details live in docs/ARCHITECTURE.md.

Questions and sponsorship

For questions, ideas, and help, use Bomly Discussions. Use this repository's issues for confirmed bugs, regressions, and concrete implementation work.

If Bomly is useful to you, star the repository, share feedback, contribute, or sponsor ongoing maintenance.

License

Bomly CLI is licensed under the Apache License 2.0.

来源:README.md,提交 956a91d

工具

4

bomly_diff

Compare dependencies between two targets. With enrich=true, the response includes possible remediation for vulnerable packages on the head side, using the same actions and optional override_advice as bomly_scan. With audit=true (requires enrich=true), it also shows introduced, resolved, and persisted policy findings. Use bomly_explain for full details about one package.

输入参数base必填head必填pathsbomauditimageenrichanalyzeexcludefail_onbaselinecontainer另有 12 个

bomly_explain

Explain why one package is present and show its dependency paths. With enrich=true, the response adds full vulnerability details and possible remediation. With audit=true (requires enrich=true), it also adds policy results. Use this after bomly_scan to inspect each affected package.

输入参数pathauditenrichanalyzeexcludefail_onpackage必填baselinemax_depthrecursivewarn_onlydeny_groups另有 8 个

bomly_plugins

List all available bomly plugins (built-in detectors, matchers, and auditors plus any installed external plugins) with their enabled/disabled state.

无需输入参数。

bomly_scan

Scan a project for dependencies and vulnerabilities. With enrich=true, the response groups vulnerability suggestions as direct-bump, transitive-override, lockfile-refresh, no-fix-upstream, or manual-review; transitive groups may include override_advice. Groups rank known-exploited issues first, then severity, EPSS, and fixability. For a security review, use enrich=true with audit=true. Then use bomly_explain for full details and paths for each package.

输入参数refurlpathauditimagescopeenrichanalyzeexcludefail_onbaselinecontainer另有 13 个

版本历史

9
  1. v0.30.1最新Oct 30, 2026
  2. v0.30.0Oct 26, 2026
  3. v0.29.0Oct 21, 2026
  4. v0.28.3Oct 20, 2026
  5. v0.28.2Oct 4, 2026
  6. v0.28.1Oct 4, 2026
  7. v0.27.1Oct 4, 2026
  8. v0.26.0Sep 17, 2026
  9. v0.25.0Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分