The inspected source shows a package-owned plugin setup and a conditional sandbox relaunch, both aligned with the package's ACP/TUI behavior. I found no source evidence of a malicious payload, credential exfiltration, or unconsented mutation of a foreign control surface.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Starting the TUI, or starting a hub with the sandbox birth marker set.
Impact
The plugin setup changes user-level plugin configuration; the relaunch permits the hub to run outside the backend sandbox. The inspected evidence does not establish malicious behavior.
Mechanism
The TUI seeding logic plans a write of a package-owned plugin file. The hub relaunch writes a temporary plist and asks launchd to start the hub with the process environment.
Evidence
dist/tui.jsdist/bin/hub.jsdist/remote/hub-sandbox.jsmartty plugin directory resolved by resolveMarttyHometemporary relaunch plist