The package's network and process behavior serves its stated Orbit connector and Codex desktop purpose. Device authorization is user initiated, and the manifest has no install-time hook that contacts a service or changes the system.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs an Orbit CLI command, completes device authorization, or explicitly runs `orbit desktop`.
Impact
Enables remote use of the user's Orbit-connected computer and Codex sessions as described by the package; no unrelated data collection or unauthorized account action was identified.
Mechanism
The CLI obtains a dedicated Orbit device token after authorization and uses it for the configured relay; the bridge forwards requests to the local Orbit service.
Evidence
User Orbit configuration directory, including `device.json` and pairing-key filesUser Codex desktop bridge directory
Network endpoints2
orbit.cubesugar.techregistry.npmjs.org