ReviewOS

also looking at this

craft-native/craft

Gate releases on shipped artifact findings

#316
Merged glennmichael123 wants to merge codex/gate-shipped-artifacts into main
11 files +454 -25
docs/VULNERABILITY_SCANNING.mdmodified+8-3
Changes to docs/VULNERABILITY_SCANNING.md
@@ -13,12 +13,17 @@ Each attempt removes previous JSON and text reports before validating its input.
1313A failed rerun therefore cannot attach a previous successful summary alongside
1414new diagnostics. Keep the input SBOM separate from the scanner's output files.
1515
16The existing severity policy is unchanged: Critical findings fail the check;
17High findings emit an explicit warning and remain release-review items. A green
16Critical findings fail the full-repository scan and block both native and npm
17publishing. High findings in that broad inventory emit an explicit warning and
18remain release-review items. Before publication, a separate scan blocks High
19or Critical findings in the built native binaries and in the exact packed npm
20archives with their resolved production dependencies. A green full-repository
1821scan is **not** release approval. Issue [#279](https://github.com/craft-native/craft/issues/279)
1922tracks the reviewed High/Critical policy and shipping-scope analysis; issue
2023[#276](https://github.com/craft-native/craft/issues/276) tracks locked dependency
21advisories. No baseline or vulnerability exemption is added by this workflow.
24advisories. Native binary scanning records exact hashes and detected components,
25but static Zig code may not be identifiable from the binary alone; retain the
26full-source review. No baseline or vulnerability exemption is added by this workflow.
2227
2328Syft and Grype Linux x64 downloads are pinned by release version and SHA-256 in
2429`.github/workflows/sbom.yml`. Tool updates must update both the asset URL and its