fuj1g0n/SARIF Dockerfile Anchor

Anchor Microsoft Defender (MDVM) container-image SARIF findings to the Dockerfile lines that introduced the packages, so GitHub code scanning can show them as pull-request inline annotations and diff gates.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jul 2, 2026
License
Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned
uses: fuj1g0n/sarif-dockerfile-anchor@345bc59da43a10e9deb91461801a84d62dc31ea0 # v0.3.0

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
sarifPath to the Defender CLI image-scan SARIF file.yes
sbomPath to the CycloneDX SBOM JSON file.yes
dockerfilePath to the Dockerfile to anchor findings to.yesDockerfile
base-severityComma-separated severities of base-image OS findings kept as inline annotations.nohigh,critical
link-transitiveAnchor transitive OS dependencies to the install line of the nearest package that pulled them in (via the SBOM dependency graph). When false, such findings fall back to the base FROM line.notrue
dockerfile-uriRepo-relative URI written into the SARIF artifactLocation (default: value of dockerfile).no""
outputPath to write the enriched SARIF (must be a file so it can be uploaded).noenriched.sarif
github-tokenToken used to download release assets when pinned to a release tag.no${{ github.token }}
namedescription
sarifPath to the enriched SARIF file.