chore(ci): enroll in org-wide secret-scan reusable workflow (Molecule-AI/molecule-core#2109) - #14
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
[Molecule-Platform-Evolvement-Manager]
3-line enrollment in the canonical secret-scan workflow shipped in EnterOS-AI/enter-os-core#2109. Defense against the #2090-class leak (a hosted-agent commit slipping a credential-shaped string into a PR — caught at the PR layer, before merge).
Pattern set lives in molecule-core; updates ride along automatically.
Side note on the rollout
While shipping this PR I noticed this repo's local clone .git/config had
https://x-access-token:ghs_*@github.com/...baked into the origin remote — exact #2090 leak vector pattern. Token had already expired (~1hr installation-token TTL) so no live exposure, but it's a real-world confirmation that the hosted-agent unsafe-clone pattern IS in active use across the org. Stripped the token locally before pushing this PR; this CI gate would catch any agent that subsequently slurped the URL intopackage.jsonvianpm init.