Skip to content

docs(sbom): remove bun caveat and follow-ups sections #3774

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
St0rmz1 merged 1 commit into from
Jun 5, 2026
+0 −21
Merged

docs(sbom): remove bun caveat and follow-ups sections #3774

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 0 additions & 21 deletions docs/sbom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,24 +33,3 @@ syft reads `pnpm-lock.yaml` directly (no `pnpm install` needed) and picks up the
```sh
syft scan dir:. -o cyclonedx-json=cloud-sbom.cyclonedx.json
```

## Other repos (kilocode, abuse) — bun caveat

syft cannot parse `bun.lock` (its lock cataloger only handles `package-lock.json`, `yarn.lock`, and
`pnpm-lock.yaml`). For bun repos you must scan an **installed** tree and explicitly enable the
package cataloger (it is tagged `image,installed` and is off by default for directory scans):

```sh
bun install --frozen-lockfile
syft scan dir:. \
--select-catalogers '+javascript-package-cataloger' \
--exclude './.git/**' --exclude './**/.turbo/**' --exclude './**/dist/**' \
-o cyclonedx-json=sbom.cyclonedx.json
```

## Follow-ups (not yet implemented)

- **Vulnerability scanning** — pair each SBOM with Grype and upload SARIF to the GitHub Security tab,
surfacing OS-package and shipped-image CVEs that Dependabot/CodeQL don't see.
- **Additional container images** — extend the `deploy-kiloclaw.yml` attestation pattern to gastown,
cloud-agent, and other images once each has a registry-push path to attest against.
Loading