Complete container dependency inventories in v0.1.3 - #59
Merged
Conversation
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.
Container SPDX files in v0.1.2 contained OS packages but omitted the compiled Rust and bundled npm dependencies. Runtime images now retain the build lockfiles under
/usr/share/modelport/sbom/, outside the dashboard web root. The pinned Syft scanner explicitly enables Cargo/npm lockfile catalogers in addition to its default image catalogers.Require the expected application package ecosystem before signing the container SBOM and completing release publication. The inventory records locked build inputs and can include workspace/build dependencies; it does not claim runtime reachability. Prepare v0.1.3 without rewriting the immutable v0.1.2 assets or tag.
Validation: