chore: protect package installs with Socket Firewall - #1695
Merged
Conversation
Contributor
|
nigel-campbell
approved these changes
Sep 10, 2026
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.
Public pull request and release jobs currently install npm packages before Socket Firewall is active. This change adds the pinned Socket Firewall action before those installs so package downloads go through the WorkOS firewall registry. For public pull requests, checkout now avoids persisted credentials and the workflow keeps read-only permissions before enabling the action's external-fork fallback.
The npm publish workflow now tears down the same pinned action after build and test, before
npm publish. The dependency-bump workflow keeps the existing version bump, lockfile, push, and pull request commands, but it now commits dependency updates while Socket Firewall is active and only pushes or opens downstream pull requests after teardown.Manual verification: inspect the edited workflows and run
actionlint -shellcheck= .github/workflows/ci.yml .github/workflows/runtime-tests.yml .github/workflows/release.yml .github/workflows/workos-node-dep-bump.yml.Testing: the edited workflows pass GitHub Actions syntax checks with
actionlint; the Socket Firewall conformance check reports no simple red flags for the changed install paths.