The lifecycle behavior is limited to platform-aware cleanup, verified binary installation, and guarded CLI alias setup. The CLI passes arguments to the native binary, and the inspected source establishes no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the declared lifecycle hooks; running the CLI invokes the native binary, with a bootstrap attempt if it is missing.
Impact
The inspected behavior supports ordinary CLI installation and invocation; no concrete harmful effect was established.
Mechanism
The postinstall obtains the platform binary from a Hanzo GitHub release and verifies its SHA-256 digest. Global alias setup checks for a conflicting `code` command before creating a wrapper.
Evidence
package.jsonscripts/preinstall.jspostinstall.jsbin/coder.js
Network endpoints1
github.com/hanzoai/dev/releases/download/v${version}/${archiveName}