AI Security Review
scanned 2h ago · by lpm-firewall-aiLPM blocks this version under the AI-agent control-surface policy. Automatic npm postinstall mutates the consuming project's AI-agent configuration surface. It drops `.vscode/mcp.json` and `AGENTS.md`, then configures a repository post-commit hook when applicable.
Decision evidence
public snapshot- `package.json` runs `postinstall` automatically.
- `bin/install-host.js` targets `INIT_CWD` or `process.cwd()`, i.e. the consuming project.
- Postinstall copies package `.vscode/mcp.json` and `AGENTS.md` into that project.
- `.vscode/mcp.json` registers six package-selected MCP server commands.
- Postinstall invokes `scripts/setup/install-project-hooks.ps1`, which sets local `core.hooksPath=.githooks`.
- Existing differing files are preserved unless `--force`, but absent control files are created without consent.
- No credential harvesting or exfiltration was found in inspected lifecycle files.
- The lifecycle path skips interactive bootstrap when stdin is non-TTY.
- The dropped MCP configuration uses local command names rather than embedded remote URLs.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgInstall-time source drops package-supplied AI-agent/MCP control files or instructions.
bin/install-host.jsView on unpkg · L1Package ships non-JavaScript build or shell helper files.
scripts/context/build-repomix.ps1View on unpkg