The user-invoked command can install and execute an unpinned CLI release, creating a real supply-chain exposure. The inspected source shows no concrete attack, and the behavior is limited to invoking the command, so this warrants a warning rather than a publish block.
Static reason
No blocking static signals were detected.
Trigger
User invokes the `furrycap` binary while `node_modules/@furrymink/cli` is missing from the current directory.
Impact
A future or changed CLI release could run shell commands with the invoking user’s privileges; no malicious behavior was established in the inspected dependency source.
Mechanism
Runs `npm install @furrymink/cli@latest`, then sources the installed CLI’s shell includes and dispatches the command.
Evidence
bin/furrycap/furrycappackage.jsoncurrent-directory `node_modules/@furrymink/cli`
Network endpoints1
npm registry (implicit via `npm install`; host not specified in source)