fix(foundation): verify repository Gitleaks policy - #37
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR: upgrade the shared Foundation scanner to the official digest-pinned Gitleaks v8.30.1 image, apply an exact repository policy to both snapshot and history scans, and make the version-specific AlmaMesh regression part of the canonical generated-client fixture.
Why: v8.29.1 missed two generic-api-key fixtures that v8.30.1 detects. The protected root CI previously did not execute the module-internal adversarial regression.
Proof: Foundation 238 passed/1 skipped at 93.93%; root 211 passed at 96.38%; real module-fixtures passed against public AlmaMesh SHA 76cfea53 with a clean exact snapshot/history plus fresh-history and no-Git snapshot negatives that each produce exactly two findings. Ruff, strict mypy, Xenon A, audits, actionlint, schema, branch floors, and independent review are green.