Route CI dependency installs through Socket Firewall - #6
Merged
Merged
Conversation
mjdavidson
approved these changes
Sep 9, 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.
The continuous integration job installs npm dependencies straight from the public registry with
npm ci, which leaves the install open to a compromised or typosquatted package reaching the runner unchecked. This change routes those downloads through the WorkOS Socket Firewall so packages are inspected before they are installed.The firewall step is placed between
actions/setup-nodeandnpm ci, the point where Node is ready but nothing has been fetched yet. It authenticates with thePUBLIC_SOCKET_FIREWALL_TOKENsecret. Because this repository is public, it also enablesallow-external-fork-fallbackso pull requests from forks, which never receive secrets, can still run their checks against the public registry. Runs onmain, dependency-update branches, and same-repo pull requests keep the firewall fully active because the token is present for them, and the action only permits the public fallback for a genuine external-fork pull request, so protection is never silently dropped on a trusted run. Theactions/checkoutstep no longer persists the Git credential, since this job only needs to read the code.To verify, open the pull request's checks and confirm the Socket Firewall step reports active before
npm ci, with install, lint, format, and type-check all passing. The dependency set, lockfile, and build commands are unchanged, so a green run means the firewall stays transparent to the existing checks.