The default release install path combines inherited npm credential variables with a fallback to a third-party registry mirror, creating a plausible credential exposure risk. The source does not show the request authentication behavior, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the publish workflow with dependency installation enabled, which is the default.
Impact
A token could reach the mirror if Bun or the user's registry configuration uses that token for mirror requests; the source does not establish that an authorization header is actually sent.
Mechanism
Registry retries include registry.npmmirror.com, and the Bun subprocess inherits the prepared environment, which retains token variables.
Network endpoints2
registry.npmmirror.com/registry.npmjs.org/