The postinstall hook contains a real, automatic shim migration that can remove another CLI's PATH entries, despite nori-code documenting only the nori command. The behavior is gated and appears to be stale migration logic, so it warrants a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A global install where PATH contains a detected Python kimi-cli shim and a kimi executable recognized as belonging to the hook's own package.
Impact
The user's existing Python CLI may stop resolving under kimi, and duplicate shims may be removed.
Mechanism
The hook renames the first detected shim to kimi-legacy and unlinks additional detected shims.
Evidence
package.jsonREADME.mdscripts/postinstall.mjsscripts/postinstall/migrate.mjsscripts/postinstall/reach.mjsPATH-resolved kimi executablePATH-resolved kimi-legacy target