Repository navigation
feat: export artifact inspection as privacy-preserving SARIF - #27
Merged
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
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.
Artifact inspection can now export SARIF 2.1.0 through
artifacts --format sarif, allowing automation to consume the same deterministic findings as local review. Results contain stable rule IDs, safe encoded relative locations and metadata-based fingerprints; raw record values, fields, free-form messages and absolute paths are omitted. Logical CSV records are not reported as physical source lines.Validation: 663 tests pass with one existing opt-in Docker skip; type checking, lint, build and the actual built CLI pass. Negative cases cover unsafe paths, setup errors and rejecting SARIF comparison mode before file access. No upload or external audit is performed.