The scanner flags correspond to release tooling: subprocess calls, environment/configuration access and npm registry requests are used by exported workflows. The package has no install hook, and the inspected entry code does not automatically invoke those workflows or send credentials to an unrelated host.
Static reason
One or more suspicious static signals were detected.
Trigger
A consumer explicitly calls exported build, publish, dependency-install, registry-check or tarball-audit functions.
Impact
Expected release and package-audit effects; inspected source did not show automatic credential disclosure or unrelated actions.
Mechanism
Those workflows may invoke Bun, read project and npm configuration, write a release baseline, or query npm registry metadata and package tarballs.
Evidence
.lzi/release/baseline.jsonbunfig.toml.npmrc
Network endpoints2
registry.npmmirror.comregistry.npmjs.org