ShipShadow proof

hisopo/go-and-do

Repository

hisopo/go-and-do

Head SHA

21c6a1156054dba1ff91bfd13148ec0b30e8fe3d

Branch

test

Status

completed

Conclusion

failure

Run

run_f9d53b1da021e7d423685b18

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	HIGH CWE-1240-ALL-005 in scripts/workerProductAcceptance.mjs HIGH CWE-325-ALL-002 in scripts/workerProductAcceptance.mjs HIGH H12 in scripts/workerProductAcceptance.mjs HIGH H12 in scripts/workerProductAcceptance.mjs HIGH CVE-2026-67214 HIGH CVE-2026-67213 HIGH GHSA-r28c-9q8g-f849 HIGH GHSA-f88m-g3jw-g9cj HIGH CVE-2026-13697 HIGH CWE-328-ALL-003 in worker/index.ts HIGH CWE-614-ALL-003 in worker/index.ts File coverage is complete for 178 changed files. Cross-file and project-level findings are batch-local because this scan was sent as 3 requests to stay within the SiteShadow per-request limits. 5 blocking findings from an earlier commit on this repository have not been resolved: HIGH CWE-1240-ALL-005 in scripts/workerProductAcceptance.mjs (introduced in dd2fd12) HIGH CWE-325-ALL-002 in scripts/workerProductAcceptance.mjs (introduced in dd2fd12) HIGH CWE-328-ALL-003 in worker/index.ts (introduced in dd2fd12) HIGH CWE-614-ALL-003 in worker/index.ts (introduced in dd2fd12) HIGH H12 in scripts/workerProductAcceptance.mjs (introduced in dd2fd12) 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.