The release workflow’s fallback to registry.npmmirror.com runs dependency installation with an environment that retains npm token variables. The source does not prove the package manager sends a token to that host, so this is a credential-handling risk warranting a warning rather than a confirmed malicious credential transfer.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the release workflow with dependency installation enabled (the default), and the registry retry logic falls back to registry.npmmirror.com.
Impact
If the package manager applies an npm credential to the mirror request, that credential reaches a host outside the npm registry service. The source does not itself construct an authenticated HTTP request, so actual credential transmission depends on package-manager auth handling and configuration.
Mechanism
The install subprocess inherits process environment values, including npm token variables. Registry override keys are filtered, but the token variables are not; the package manager may use configured credentials for requests to the fallback registry.
Network endpoints2
registry.npmmirror.comregistry.npmjs.org