Skip to content

chore: add security policy, job-scoped release permissions, pin first-party actions#77

Merged
lan17 merged 1 commit into
mainfrom
chore/security-hardening
Jul 21, 2026
Merged

chore: add security policy, job-scoped release permissions, pin first-party actions#77
lan17 merged 1 commit into
mainfrom
chore/security-hardening

Conversation

@lan17

@lan17 lan17 commented Jul 21, 2026

Copy link
Copy Markdown
Owner

Targets three Scorecard point losses measured on the 2026-07-21 run (overall 5.1):

  • Token-Permissions 0 → 10 (high weight): release.yaml granted contents: write + id-token: write at the workflow level; now permissions: {} top-level with writes scoped to the release job. No behavior change.
  • Security-Policy 0 → 10: SECURITY.md with private-vulnerability-reporting instructions (PVR is now enabled on the repo) plus the trust-model notes from the security-surface review (Redis is trusted, key encoding guarantees, metrics label constraints).
  • Pinned-Dependencies 8 → 10: actions/checkoutd23441a4 (v6.1.0), actions/setup-node24997072 (v6.5.0). Every action in every workflow is now SHA-pinned; after this merges the repo's sha_pinning_required setting can be flipped to enforce it.

🤖 Generated with Claude Code

…n first-party actions

Token-Permissions: release.yaml now grants contents/id-token write at
the job level only. Pinned-Dependencies: actions/checkout and
actions/setup-node join the SHA-pinned set, completing hash pinning
across all workflows. SECURITY.md documents private vulnerability
reporting (now enabled) and the Redis-is-trusted model.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lan17
lan17 merged commit be398c9 into main Jul 21, 2026
5 checks passed
@lan17
lan17 deleted the chore/security-hardening branch July 21, 2026 02:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant