Fix pinned archive installs through Socket Firewall - #167
Draft
peakematt wants to merge 1 commit into
Draft
Conversation
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
1 participant
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.
OpenAPI’s protected
npm cifails because Socket Firewall’s user-levelreplace-registry-host=alwayssetting also rewrites the pinnedtree-sitter-kotlinGitHub archive ontosocket-firewall.workos.dev. That archive path is not an npm package endpoint, so the request returns 404 and blocks publishing and spec-change recording.Set
replace-registry-host=npmjsin the existing project.npmrc. Project configuration takes precedence over the firewall’s user configuration, so this covers the repository’s installs without repeating overrides across workflows. Public npm tarballs still use the configured firewall registry; the existing GitHub archive stays a direct, integrity-checked download, not Socket-inspected traffic. Its pinned commit and integrity, all dependency versions, registry/authentication settings, DNS blocking, and release teardown are unchanged.From the repository root, with npm already installed:
npm config get replace-registry-host # npmjsOffline checks with npm 11.19.0 and its bundled pacote 21.5.1 reproduced the old host rewrite and verified that the new setting preserves the archive URL/integrity while routing scoped and unscoped npm tarballs through the configured firewall.
git diff --checkpasses. No dependency install or release was run locally. The existing PR workflow skips dependency installation when the spec is unchanged, so its success alone does not establish a live protected-install result; that remains for the next applicable workflow run.Related: https://linear.app/workos/issue/HELP-725