The updater is reachable by default and can install a newer global copy, but it targets bkper itself through the npm registry and provides the BKPER_DISABLE_AUTOUPDATE off-switch. Under the current self-update rule this warrants a warning, not a publish block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Ordinary CLI startup, once per daily interval; disabled by BKPER_DISABLE_AUTOUPDATE or CI.
Impact
The package can update itself without a separate update command. The current rules treat this same-package npm self-update with an off-switch as suspicious, not malicious.
Mechanism
A detached worker checks registry.npmjs.org/bkper/latest and installs a newer bkper version when the running copy is a verified writable global installation.
Evidence
lib/cli.jslib/upgrade/update-check.jslib/upgrade/installation.jsBkper update-check cache under BKPER_CONFIG_DIR/update-check/The global bkper installation selected by its package manager
Network endpoints1
registry.npmjs.org/bkper/latest