create-chemx@26.9.16-1408
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest-triggered postinstall path makes unconsented changes to consumer and user-level AI-agent control configuration. This meets the policy for blocking an automatic lifecycle mutation of a foreign agent control surface.
Decision evidence
public snapshot- package.json defines a postinstall hook that runs cli/postinstall.js.
- The postinstall hook targets the consuming project and calls the MCP installer without a consent prompt.
- The installer writes MCP configuration into the project's Cursor and VS Code agent directories.
- When the user-level Gemini configuration directory exists, the installer also writes an MCP server entry there.
- The added server entry launches the chemx MCP command, and the installer may add a chemx:mcp script to the consumer package.json.
- The separate installer wizard presents an explicit choice before installing MCP configuration; that prompt does not guard the automatic postinstall path.
- The package also offers MCP setup through a user-facing installer wizard, where the user selects whether to install it.
Source & flagged code
9 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 unpkgPackage source references child process execution.
cli/audit-preflight-git.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to create-chemx@26.9.16-1408.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing create-chemx@26.9.16-1408. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.