From 0c3975cb2fbd40557685c8247c75ed533f179a0e Mon Sep 17 00:00:00 2001 From: Ahmed ElMallah Date: Sun, 1 Nov 2026 23:00:43 -0800 Subject: [PATCH 1/2] docs(integrations): say the editor path is MCP plus SARIF, no extension Visitors looking for a VS Code or Cursor extension found nothing that said one does not exist. Add an entry under AI agents and editors that points at the MCP guide, the SARIF output, and the pre-commit hook. Co-Authored-By: Claude Fable 5.1 --- docs/INTEGRATIONS.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/INTEGRATIONS.md b/docs/INTEGRATIONS.md index b15c5ef9..37b198b6 100644 --- a/docs/INTEGRATIONS.md +++ b/docs/INTEGRATIONS.md @@ -26,6 +26,11 @@ Copy-and-paste recipes for GitHub Actions, GitLab CI, Jenkins, Azure DevOps, and A ready-made instruction for `CLAUDE.md`, `AGENTS.md`, or `copilot-instructions.md` that makes a coding agent run a dependency diff before it commits lockfile changes. → [MCP Server → Example prompts](MCP.md#example-prompts) +### Editors: VS Code and Cursor (Official) + +There is no Bomly editor extension, and none is planned. The editor path is MCP plus SARIF: connect the MCP server so the editor's agent can scan, explain, and diff, and open `bomly scan --format sarif` output in a SARIF-aware viewer for inline findings. The pre-commit hook catches lockfile changes before they leave the machine. +→ [MCP Server](MCP.md) · [Output formats → SARIF](OUTPUT_FORMATS.md#sarif) · [CI Integration → Pre-commit hook](CI_INTEGRATION.md#pre-commit-hook) + ## GitHub code scanning Bomly writes SARIF 2.1.0, which the GitHub Security tab and other SARIF-aware tools read. Upload it through Guard's `upload-sarif` input or from the CLI. From 078d1aca0fdc1bf74efaf55c9c127a130120b039 Mon Sep 17 00:00:00 2001 From: Ahmed ElMallah Date: Sun, 1 Nov 2026 23:08:06 -0800 Subject: [PATCH 2/2] docs(integrations): fix the SARIF command and hook stage in the editor entry The SARIF example lacked --audit, which the CLI requires. The hook runs at pre-push, not on lockfile changes. Sentences split to stay short. Co-Authored-By: Claude Fable 5.1 --- docs/INTEGRATIONS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/INTEGRATIONS.md b/docs/INTEGRATIONS.md index 37b198b6..ff39dc7d 100644 --- a/docs/INTEGRATIONS.md +++ b/docs/INTEGRATIONS.md @@ -28,7 +28,7 @@ A ready-made instruction for `CLAUDE.md`, `AGENTS.md`, or `copilot-instructions. ### Editors: VS Code and Cursor (Official) -There is no Bomly editor extension, and none is planned. The editor path is MCP plus SARIF: connect the MCP server so the editor's agent can scan, explain, and diff, and open `bomly scan --format sarif` output in a SARIF-aware viewer for inline findings. The pre-commit hook catches lockfile changes before they leave the machine. +There is no Bomly editor extension, and none is planned. The editor path is MCP plus SARIF. Connect the MCP server so the editor's agent can scan, explain, and diff. For inline findings, run `bomly scan --enrich --audit --format sarif` and open the file in a SARIF-aware viewer. The pre-commit framework hook runs a scan at the `pre-push` stage, before changes leave the machine. → [MCP Server](MCP.md) · [Output formats → SARIF](OUTPUT_FORMATS.md#sarif) · [CI Integration → Pre-commit hook](CI_INTEGRATION.md#pre-commit-hook) ## GitHub code scanning