Source inspection found a local, token-authenticated hub upgrade notification and a sandbox-marker-gated launchd relaunch. Flagged runtime files resolve Node/Bun for package operation; the scanner hints do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The postinstall hook runs after package installation; sandbox relaunch is triggered only when the hub inherits the sandbox-active marker.
Impact
The observed behavior supports local hub upgrade checking and sandbox operation; no malicious effect was established.
Mechanism
The hook sends a bearer-authenticated POST to the configured local hub, which checks authorization and determines whether its on-disk code is newer. The relaunch path writes a launchd plist only for a hub born inside the sandbox.
Evidence
package.jsondist/remote/hub-upgrade-notify.jsdist/remote/hub-server.jsdist/remote/hub-sandbox.jsdist/bin/hub.jsdist/backend/resolve.jsdist/runtime.js