The lifecycle behavior is limited to configuring botmux’s own global launcher and PATH, with guards for local installs and source checkouts. The launcher dispatches to the matching optional botmux binary, and the inspected source establishes no malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A package manager runs postinstall during installation; the script proceeds only when the install is identified as global and outside the source checkout.
Impact
The installed botmux command becomes available in future shells; inspected behavior does not establish an attack.
Mechanism
It locates the matching platform binary, writes a launcher under ~/.botmux/bin, and adds that directory to the detected shell’s startup configuration.
Evidence
~/.botmux/bin/botmuxuser shell startup file