Repository navigation
feat(standards): audit dependency alerts, deploy keys, webhooks and actions - #22
Merged
Merged
Conversation
…ctions New read-only rules: dependabot-alerts (off), dependabot-overdue (open alert with a patched version past 7/30/90 days for critical/high/medium), deploy-key-write, webhook-secret, branch-protection on public repositories and actions-allowlist for the organisation (restricted list, SHA pinning). All warnings or info, so a CI step with --fail-on error keeps its meaning. The audit reports and never changes keys, webhooks or two-factor.
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
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.
What
Six new read-only rules in
standards/audit.py:dependabot-alerts,dependabot-overdue(7/30/90 days for critical/high/medium, only when a patched version exists),deploy-key-write,webhook-secret,branch-protection(public repositories) andactions-allowlist(organisation).Why
Spec
next-org-security-baseline(FR1, FR2, FR4 to FR6): the weekly report should show these gaps so they cannot drift. Severities arewarningorinfo, so--fail-on errorkeeps its meaning.Verification
ghcalls).brandbookswith no CI, Dependabot or branch deletion.