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