The postinstall hook automatically runs setup, which can install and enable Obsidian plugins. This warrants a warning for lifecycle-triggered extension setup, but the inspected source does not establish a block-level attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package with npm, which invokes its postinstall hook.
Impact
Installation can add and enable plugins in the user’s Obsidian vault without a separate confirmation for that step.
Mechanism
The installer proceeds without an interactive prompt and creates the vault; plugin setup fetches release assets and writes plugin IDs to Obsidian’s enabled-plugin list.
Evidence
package.jsoninstall/install.mjssrc/commands/second-memory.tsdist/commands/second-memory.js