Backport to 26.3: PackageLockJsonTest allow "npm:" alias transitive dependencies (#2995)#3095
Merged
labkey-martyp merged 1 commit intoJul 9, 2026
Conversation
…"npm:" alias prefix (#2995)
labkey-tchad
approved these changes
Jul 9, 2026
cnathe
approved these changes
Jul 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
3 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.
Rationale
Cherry-pick of #2995 to release26.3-SNAPSHOT. Packages that declare npm-aliased dependencies (e.g.
npm:react-is@^18.3.1) are legitimate registry references, but the pre-#2995 version of the test flags them as untrusted sources.Related Pull Requests
Changes
npm:alias prefix instead of the hard-coded allow-list; still flags URL, file, git, and workspace specs.server/modules.