feat(agent): per-artifact vulnerabilities/violations in agent release show - #26
Merged
Merged
Conversation
… show A release carries multiple SBOMs/scan results — a clean source-code SBOM and a vulnerable deliverable/container SBOM (plus SARIF / VDR) — so the release-level aggregate alone left agents unable to localize findings. agent release show now walks every artifact's own metrics: sourceCodeEntryDetails.artifactDetails (source SBOMs), artifactDetails (release-level), and variantDetails[].outboundDeliverableDetails[] .artifactDetails (deliverable SBOMs / scan results) — each with its counts + vulnerabilityDetails + violationDetails. Release-level metrics (with details) stay on top. Release-level metrics reflect release-scope vuln suppressions while per-artifact metrics are raw, so the two detail lists can differ — both are kept on purpose. agenticReleaseProgrammatic already returned the full Release; this only expands the selection. Validated against a real session-built release (source SBOMs + deliverable artifacts resolve). ReARM-Agentic-Session: agent-per-artifact-vulns-1780060789 ReARM-Agent: 62df357e-a3a4-4df5-82d4-049e629d1c6b Co-Authored-By: Claude Opus 4.7 (1M context) <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
2 participants
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.
Summary
A release carries multiple SBOMs / scan results — a (typically clean) source-code SBOM and the (often vulnerable) deliverable/container SBOM, plus SARIF (
CODE_SCANNING_RESULT) and VDR. The release-level aggregate alone left agents unable to localize findings (the reported confusion: "source SBOM is clean but the deliverable isn't, and the agent didn't know there was a deliverable SBOM").agent release shownow walks every artifact's ownmetrics, mirroring the UI's artifact set:sourceCodeEntryDetails.artifactDetails— source-code SBOMs / SARIF;artifactDetails— release-level artifacts;variantDetails[].outboundDeliverableDetails[].artifactDetails— deliverable SBOMs / scan results;each with severity counts +
vulnerabilityDetails[]+violationDetails[]. The release-levelmetrics(with details) stays on top.Kept duplication on purpose: release-level metrics reflect release-scope vuln suppressions while per-artifact metrics are raw, so the two detail lists can legitimately differ — surfacing both is the v1 behavior (documented in orientation).
No backend change —
agenticReleaseProgrammaticalready returns the fullRelease; this only expands the query selection. Covers all artifact types (BOM / SARIF / VDR), not just BOMs.Test plan
go buildpasses.sourceCodeEntryDetails.artifactDetails(4) andvariantDetails[].outboundDeliverableDetails[].artifactDetailsresolve, each withmetrics; no GraphQL errors.vulnerabilityDetailslocalizes them while the source SBOM shows clean.Pairs with an orientation.md update (rearm-saas) explaining the multi-SBOM structure + the suppression quirk.