ShipShadow proof

hisopo/go-and-do

Repository

hisopo/go-and-do

Head SHA

527379e8ba9018a893797d1be53cc9f83e5e34cb

Branch

dev

Status

completed

Conclusion

failure

Run

run_69598d6bdd1ea0e79edd8704

Gate Results

Gate	Conclusion	Summary
ShipShadow / CR Routing Gate	failure	This changeset has routed paths but no changed or cited change-record document. This check is advisory.
ShipShadow / Change Request Gate	failure	No configured pull request field contains a valid change request identifier. This check is advisory.
ShipShadow / Policy Gate	success	No blocked workflow or release-evidence policy violations were found.
ShipShadow / Publish Gate	failure	Publication is blocked by: ShipShadow / Security Gate.
ShipShadow / Secret Gate	success	Changed-file content passed the ShipShadow secret gate.
ShipShadow / Security Gate	failure	12 blocking findings from an earlier commit on this repository have not been resolved: HIGH CWE-89-ALL-005 in scripts/workerProductAcceptance.mjs (introduced in dd2fd12) HIGH CWE-89-ALL-006 in scripts/workerProductAcceptance.mjs (introduced in dd2fd12) HIGH H12 in scripts/workerProductAcceptance.mjs (introduced in dd2fd12) 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) HIGH CWE-79-002 in public/kingdoms/admin.html (introduced in 7404c86) HIGH CWE-88-ALL-001 in docs/qc/lina-qc-bible-21-24-2026-08-21/capture-driver.mjs (introduced in 0787ef0) HIGH CWE-476-ALL-003 in docs/qc/lina-bible-1-4-visual-2026-08-22/launch-affordances.mjs (introduced in a0a5f73) 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.