Repository navigation
Consume qualified Ubuntu security packages in the agent runtime base - #365
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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
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.
The Python node-agent runtime base still includes Ubuntu packages with upstream security fixes. Prepare
node-agent-base:v0.3.7to consume the digest-pinned Ubuntu security bundle only in the final runtime, preserving the Python compiler inputs, existing packages, coreutils provider and configuration.The publisher retains the original full Trivy report, verifies the actual image SBOM against the original bundle checksums and applies its exact-package OpenVEX before the existing pip-vendor interpretation. Eight focused package-consistency tests pass, including unrelated drift, invalid package selection and modified qualification rejection. The checker accepts inventory content through standard input and returns its result through standard output, without accepting filesystem paths. The existing wrapper continues its published-base checks until its new base is published and pinned in a subsequent change.
Publication remains pending completion of the existing bundle's SBOM attestation and anonymous readback. Its immutable digest is
sha256:2742a3d429e4e14bc587f6dedc51ded4246cf90bbaedcd86c67d0885e32a6f2a; no runtime patch or production deployment is involved. Native package suites already passed and are not rerun here. The main-only publisher must pass its Python, TLS, credential-file, SBOM and security gates before publication.