docs(sbom): separate distributed runtime from build-time toolchain - #688
Merged
Conversation
SBOM.md previously published the full `pip freeze` of the dev virtualenv (~140 packages incl. anthropic, openai, langchain, grpcio, poetry, twine, mypy) as if it were the product's SBOM. None of those ship: the distributed package declares `dependencies = ["pyyaml>=6.0.1"]`, and the container image installs only PyYAML. Presenting the dev freeze as the SBOM overstates the attack surface and misrepresents the software to anyone reading it as a compliance artifact. - Lead with the RUNTIME (distributed) set: CPython + PyYAML, plus optional extras. - Add machine-readable CycloneDX 1.5 `sbom.cdx.json` (purls, SHA-256, dependency graph) — closes the NTIA gaps the old file marked "Not Provided". - Retain the dev/CI freeze, clearly labeled as NOT distributed, for transparency. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
tcconnally
added a commit
that referenced
this pull request
Aug 30, 2026
) SBOM.md previously published the full `pip freeze` of the dev virtualenv (~140 packages incl. anthropic, openai, langchain, grpcio, poetry, twine, mypy) as if it were the product's SBOM. None of those ship: the distributed package declares `dependencies = ["pyyaml>=6.0.1"]`, and the container image installs only PyYAML. Presenting the dev freeze as the SBOM overstates the attack surface and misrepresents the software to anyone reading it as a compliance artifact. - Lead with the RUNTIME (distributed) set: CPython + PyYAML, plus optional extras. - Add machine-readable CycloneDX 1.5 `sbom.cdx.json` (purls, SHA-256, dependency graph) — closes the NTIA gaps the old file marked "Not Provided". - Retain the dev/CI freeze, clearly labeled as NOT distributed, for transparency. Co-authored-by: tcconnally <hermes@perseus.observer> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
SBOM.md published a full
pip freezeof the development virtualenv — ~140 packages includinganthropic,openai,langchain-*,grpcio,cryptography,poetry,twine,mypy— as if it were the product's SBOM.None of those ship:
dependencies = ["pyyaml>=6.0.1"](seepyproject.toml).perseus.py's only hard third-party import isyaml.requirements-runtime.txt(PyYAML alone).Publishing the dev freeze as the SBOM overstates the attack surface and misrepresents the software to anyone consuming it as a federal compliance artifact — precisely where it matters most (procurement, Iron Bank/ATO review).
Change
[mcp],[dev]).sbom.cdx.json(CycloneDX 1.5) with package URLs, SHA-256, and a dependency graph — closing the NTIA elements the old file explicitly marked "Not Provided" (SPDX/unique ID, hashes, machine-readable format).No code changes.
🤖 Generated with Claude Code