You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 95cf2e9
Browse filesBrowse the repository at this point in the historyBrowse files
// When extracting a registry-resolved package, the spec we hand to pacote is name@URL.
883
883
// pacote re-parses that with npa and gets spec.type === 'remote', so without an override the allow-remote gate would fire on every registry tarball (both =none and =root mis-fire).
884
-
// Returns true only when we are confident this is a registry-mediated install: the node's inbound edges must all be registry-typed (no exotic spec smuggled the URL in) AND the resolved URL's host must match the registry npm-registry-fetch selected for this spec, so a tampered lockfile pointing at an attacker host still hits the gate.
884
+
// Returns true only when we are confident this is a registry-mediated install.
885
885
#isRegistryResolvedTarball (node){
886
886
if(!node.resolved||!node.isRegistryDependency){
887
887
returnfalse
888
888
}
889
889
try{
890
-
// Hostnames are case-insensitive; lowercase both sides for safety even though WHATWG URL already normalizes.
0 commit comments