The postinstall performs first-party Pi integration setup, which warrants a warning under the lifecycle policy. The bundled executable remains unresolved, but the inspected source does not establish malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall hook.
Impact
This creates a package-owned agent integration; the executable’s behavior remains unverified.
Mechanism
The installer writes a named server entry to Pi’s MCP configuration and installs a bundled executable in the user’s local bin directory.
Evidence
install.js~/.pi/agent/mcp.json~/.local/bin/pi-google-services