[sec] Fix npm registry — replace public registry with CodeArtifact#72
Open
revisai[bot] wants to merge 1 commit into
Open
[sec] Fix npm registry — replace public registry with CodeArtifact#72revisai[bot] wants to merge 1 commit into
revisai[bot] wants to merge 1 commit into
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
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.
What was detected
This repository ships configuration that resolves npm packages from the public
registry (
registry.npmjs.org), exposing builds to supply-chain attacks.Files changed by this PR
.npmrc(create)After merging
Regenerate and commit your lockfile (
npm install/yarn install/pnpm install) so itresolves packages from CodeArtifact, not the public registry.
Why this matters
The public npm registry exposes the supply chain to dependency confusion, package hijacking,
and malicious package injection — any of which can silently compromise builds and production.
Migrating to the internal CodeArtifact mirror eliminates that exposure.
Questions? Reach out on
#squad-application-security.