The postinstall path automatically downloads and enables third-party Obsidian plugins, creating a guarded extension lifecycle risk. The inspected source does not establish a concrete malicious attack, so warn rather than block.
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
Third-party plugin code may be installed and activated in the user's Obsidian vault without a separate plugin-install confirmation.
Mechanism
Setup invokes second-memory initialization, which downloads plugin assets from configured GitHub latest-release URLs and adds those plugins to the vault's enabled list.
Evidence
package.jsoninstall/install.mjssrc/commands/second-memory.tscatalog/vault-structure.json
Network endpoints1
github.com/{plugin.repo}/releases/latest/download