Repository navigation
ci: route npm installs through Socket Firewall - #71
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
peakematt
marked this pull request as ready for review
September 9, 2026 00:27
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
 The PR appears safe to merge, with no actionable regression identified in the changed workflow.
|
nigel-campbell
approved these changes
Sep 10, 2026
This branch was successfully deployed
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
2 participants
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.
GitHub Actions currently installs npm packages directly in CI. This changes the CI job so npm installs run through Socket Firewall while keeping the existing Node version, npm cache, and validation commands intact.
The workflow uses the public Socket Firewall token and enables the action's validated external-fork fallback for the low-privilege pull request job. Checkout no longer persists credentials, so forked pull request jobs keep read-only GitHub permissions.
Manual verification: open the CI run for this pull request and confirm Socket Firewall setup completes before
npm ci, then the normal lint, format, typecheck, and build steps pass. I also validated the workflow syntax and Socket Firewall placement before opening this draft.