LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The manifest has no install hook, and source traces the flagged writes, downloads, and process execution to explicit CLI commands or workflow scripts. The inspected behavior is consistent with project setup and development tooling, so the scanner signals do not establish an attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes a named CLI command such as init, update, install-deps, or setup-wsl-browser.
Impact
These operations configure the project or user-requested development tooling; inspected code does not establish malicious behavior.
Mechanism
The CLI scaffolds project files, registers documented MCP integrations, or installs selected development tools; setup is not triggered by npm installation.
Evidence
package.jsonbin/dev-workflow.jslib/init.jslib/mcp.jslib/hooks.jslib/install-deps.jslib/install-open-design.jslib/setup-wsl-browser.jsscaffold/scripts/hooks/session-cost.mjsscaffold/scripts/functional-doc/generate-dossier.mjs