Source inspection confirms automatic, noninteractive setup from postinstall, including agent integration and plugin installation. This is a guarded-by-scope package-owned lifecycle setup risk, not evidence of a confirmed malicious attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package through npm runs its postinstall hook.
Impact
This can make package-owned agent integration and plugin changes during dependency installation without an interactive confirmation.
Mechanism
The hook passes --yes to the installer; the installer invokes second-memory initialization, which fetches plugin assets from GitHub and enables them in the vault.
Evidence
package.jsoninstall/install.mjssrc/commands/second-memory.ts
Network endpoints1
github.com/${plugin.repo}/releases/latest/download