Repository
hisopo/go-and-doShipShadow proof
hisopo/go-and-do
Gate Results
| Gate | Conclusion | Summary |
|---|---|---|
| ShipShadow / Policy Gate | action_required | Protected release paths changed (migrations/0004_billing_provider_seam.sql, src/data/missionLoader.ts, src/i18n/bible.ts, src/i18n/locales/ar.json, src/i18n/locales/en.json, src/i18n/locales/es.json, src/i18n/locales/fr.json, src/i18n/locales/hi.json, src/i18n/locales/it.json, src/i18n/locales/ja.json, src/i18n/locales/ko.json, src/i18n/locales/ms.json, src/i18n/locales/pt.json, src/i18n/locales/th.json, src/i18n/locales/zh.json, src/i18n/productUi.ts, src/productMissionBounds.ts, src/render3d/characterAssets.ts, src/render3d/worldAssets.ts, src/systems/Entitlements.ts, src/ui/books.ts, src/ui/journey.ts, src/ui/menu.ts, src/ui/mobilePreview.ts, src/ui/ui.css). Add .shipshadow/release-evidence.md with the verification evidence for this publication. |
| ShipShadow / Publish Gate | failure | Publication is blocked by: ShipShadow / Security Gate, ShipShadow / Policy Gate. |
| ShipShadow / Secret Gate | success | Changed-file content passed the ShipShadow secret gate. |
| ShipShadow / Security Gate | failure | HIGH CWE-451-ALL-003 in src/ui/ui.css File coverage is complete for 42 changed files. Cross-file and project-level findings are batch-local because this scan was sent as 2 requests to stay within the SiteShadow per-request limits. 6 blocking findings from an earlier commit on this repository have not been resolved: HIGH CWE-326-ALL-005 in src/i18n/bible33Phrases.json (introduced in 9c4e8f2) HIGH CWE-326-ALL-005 in src/i18n/mission24Phrases.json (introduced in 48853e3) HIGH CWE-326-ALL-005 in src/i18n/mission26Phrases.json (introduced in 48853e3) HIGH CWE-451-ALL-003 in src/ui/ui.css (introduced in 575b1ae) HIGH CWE-338-ALL-001 in scripts/qc/lina-bom-chapters-5-8/captureBand.mjs (introduced in e061078) HIGH CWE-338-ALL-001 in scripts/qc/lina-bom-chapters-5-8/recaptureClear.mjs (introduced in e061078) This commit did not change the file, so ShipShadow did not re-scan it and the finding still stands. Resolve it by fixing the file - the next run that changes it will re-scan and clear the finding - or, if it is a confirmed false positive, adjudicate it in the installation FP registry or reproduce a reviewed content-bound override with a fresh scan. |