The install hook performs first-party setup without an interactive confirmation, and the plugin feature can install release assets when explicitly requested. The inspected sources do not establish a concrete attack, so this warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installing the package through npm triggers postinstall; the separate plugin download requires the plugins option in second-memory setup.
Impact
The postinstall setup can modify the user’s local agent environment. The opt-in plugin feature adds third-party plugin files to a vault; no concrete malicious behavior was established in the inspected code.
Mechanism
The install hook runs install/install.mjs with --yes. The second-memory installer fetches assets from each configured GitHub release and writes them into the vault’s plugin directory.
Evidence
install/install.mjssrc/commands/second-memory.tsdist/commands/second-memory.jspackage.json
Network endpoints1
github.com/${plugin.repo}/releases/latest/download