Skip to content

feat(security): npm bootstrap path, exact npm pin, and release rulesets #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Radiergummi merged 1 commit into from
Jul 30, 2026
Merged

feat(security): npm bootstrap path, exact npm pin, and release rulesets #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,9 @@ permissions: {}

env:
# Trusted publishing needs npm 11.5.1 or newer. setup-node bundles whatever shipped with the Node
# release, so the version is pinned explicitly rather than left to chance.
NPM_VERSION: '11'
# release, so the version is pinned to an exact patch rather than left to a floating major. Renovate
# keeps it current.
NPM_VERSION: '12.0.2'

jobs:
verify:
Expand Down
6 changes: 4 additions & 2 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,8 +104,10 @@ Stated explicitly rather than left for someone to discover:
- **Secret scanning is currently disabled** by an organisation-level security configuration, which a
repository administrator cannot override. It is free for public repositories and should be enabled
org-wide.
- **Immutable releases** are not currently exposed through the REST API, so the setting must be
confirmed in the repository's UI under Settings → General.
- **Immutable releases** are not exposed through the REST API. A repository ruleset covers the
important half: `refs/tags/v*` cannot be deleted, updated, force-pushed, or created unsigned, so a
published version tag cannot be moved to different code. Confirm the GitHub-native setting in
Settings → General as well, if it is available to the organisation.
- **No egress filtering on runners.** `step-security/harden-runner` is the usual recommendation and
would detect a build step phoning home. It is deliberately absent: adding a third-party action to
the publish path widens the trusted set on exactly the job where that matters most. Worth revisiting
Expand Down
Loading