The postinstall action is limited to a bearer-authenticated request to a configured loopback hub, which independently checks whether newer package code is present before restarting. The flagged launchd behavior relaunches the package's own hub only when sandbox constraints require it, and quota credentials are used for the provider quota feature.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The notifier runs on npm postinstall; the hub relaunch path runs only when the hub detects it was started inside the package's sandbox.
Impact
The hub may restart onto newer package code, quota usage is retrieved, and the hub can continue outside the sandbox. No unrelated collection or harmful action was found.
Mechanism
The notifier sends an authenticated upgrade check to a configured loopback hub. Quota requests send the active ZCode provider key to that provider's quota API. The sandbox path starts the package's own hub once through launchd.
Evidence
package.jsondist/remote/hub-upgrade-notify.jsdist/remote/hub-server.jsdist/remote/hub-sandbox.jsdist/bin/hub.jsdist/quota/client.js