The package has no lifecycle scripts, and it does not connect when the Iridium URL is unset. Its runtime capabilities are tied to a user-configured service and first-time pairing approval, with code that masks secret environment values and denies access to common credential files.
Static reason
No blocking static signals were detected.
Trigger
The plugin starts with an Iridium URL configured by the user; first-time pairing requires approval on the Iridium page.
Impact
An approved Iridium can use the executor to run requested sessions and access permitted files, as intended by the package.
Mechanism
It sends pairing and protocol requests to that configured service, masks secret environment values in its hello message, and restricts file access to exclude credential paths.
Evidence
$DSH_HOME/remote-iridium/~/.dsh/remote-iridium/
Network endpoints3
Configured Iridium host: /api/exec/pairConfigured Iridium host: /api/exec/pair/{request}Configured Iridium host: /api/exec (WebSocket and token-check request)