The global postinstall can rename or delete existing Python kimi shims, while the package exposes a nori command and does not disclose this side effect in its README. Its narrow migration checks and the CLI’s legacy migration feature provide context, but do not establish user consent for changing those commands during installation.
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
Installing nori-code globally, when the PATH checks find an owned `kimi` command and detected Python `kimi-cli` shims.
Impact
An existing Python Kimi CLI command may be renamed or removed without a separate request to change that command.
Mechanism
The hook renames the first detected shim to `kimi-legacy` when possible and unlinks additional detected shims; it can also unlink a shim when its rename target is occupied by a user-managed file.
Evidence
package.jsonscripts/postinstall.mjsscripts/postinstall/migrate.mjsPATH entries named `kimi` and `kimi-legacy`