Repository navigation
ci: qualify published scanner receipts on a real consumer - #78
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 48 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|



Change
Run this repository's actual
Secret Scannercaller at the published source8d94c37463ccdba24810da488364a7c3f82aea37, which includes the reviewed exact-placeholder correction from #81. The directjobs.scan.usescontract,contents: read,fast-pr: false, and full-history/tree coverage remain in effect.The branch now includes current published main plus the single consumer-pin change. The implementation checkout is bound to the published source SHA.
Actual suite consumer evidence
Subject:
5bc8706bc53ee1980d2d99ba1f57d7ba374d5304.Secret Scanner run 41887426095 completed successfully:
hyperpolymath/cicd-suite@8d94c37463ccdba24810da488364a7c3f82aea37SUBJECT_SHAandEXPECTED_SHAequal the subject above; upstream result successscan / gitleaks,scan / rust-secrets,scan / shell-secretsThis evidence was read from the actual producer and receipt-consumer job logs, not inferred from an overall green rollup. The workflow does not publish a separate artifact; its per-detector completion outputs are checked by the compatibility jobs.
Paired consumer gate
The coordinated Echidna run at the same published source must be inspected and compared before merging this qualification PR or retiring any redundant workflow. Its final current-head receipt is pending. Earlier-source results and local fixtures do not substitute for that comparison. These scanner results are limited to their recorded source, subject and scope; they do not establish general security or qualify the later namespace change in #82.