The lifecycle behavior is automatic but package-aligned: the source and README identify it as setting up Orb's own user store. The inspected wrapper source establishes no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package runs its postinstall hook; ordinary CLI behavior starts when a user invokes orb.
Impact
The evidenced effect is setup of Orb's user store; no unrelated recipient or foreign control-surface mutation is established by the inspected source.
Mechanism
The hook runs `update --global` only when the platform binary and bun are available. The package describes this as Orb setup, and the CLI wrapper forwards the user's arguments to the Orb binary.