The postinstall hook automatically writes the package's launcher and a PATH entry into shell startup files, a behavior the review rules classify as suspicious. The launcher serves the package's CLI, but a broad pnpm path check may also trigger this setup for a local dependency.
Static reason
One or more suspicious static signals were detected.
Trigger
The postinstall hook runs when the install-location check identifies a global install; the broad `/.pnpm/` match can also accept a local pnpm package path.
Impact
Future shells may resolve `botmux` to the installed package binary. The change is intended to expose this package's CLI, but occurs automatically during installation.
Mechanism
The hook writes `~/.botmux/bin/botmux`, then appends a PATH entry to a shell startup file so future shells can find it.
Evidence
package.jsonscripts/postinstall-bin.mjsscripts/install-path-entry.mjs~/.botmux/bin/botmux~/.zshenv~/.bashrc~/.bash_profile~/.bash_login~/.profile~/.config/fish/conf.d/botmux.fish