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 分