Repository navigation
chore: harden public driver repository - #1
Conversation
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 995d38405c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| + b"[A-Za-z0-9+/=\\r\\n]{100,}" | ||
| + b"-----END [A-Z0-9 ]*PRIVATE KEY-----" | ||
| ), | ||
| "GitHub token": re.compile(b"gh" + b"[opsu]_[A-Za-z0-9]{20,}"), |
There was a problem hiding this comment.
Catch fine-grained GitHub PATs in the history scan
This only matches the older ghp_/gho_/ghs_/ghu_ token prefixes, so a fine-grained GitHub PAT beginning with github_pat_ can be committed anywhere in history and this new CI job still reports success. Since the job is meant to reject GitHub tokens from Git history, include the current github_pat_ form as well or these credentials will slip through the added hardening.
Useful? React with 👍 / 👎.
Summary
Validation
Control remains disabled. This PR does not publish or sign a driver artifact.