create-chemx@26.9.16-1249
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest activates a postinstall script that automatically writes MCP configuration into consumer project and user-level agent control files without consent. This is a concrete install-time control-surface mutation, so the package should be blocked.
Decision evidence
public snapshot- package.json runs cli/postinstall.js as an npm postinstall hook.
- The hook automatically invokes installAllMcpConfigs for the consumer directory.
- The installer writes MCP server configuration into project-level .cursor/mcp.json and .vscode/mcp.json.
- When a Gemini config directory exists, the installer also writes to the user-level ~/.gemini/config/mcp_config.json.
- No consent prompt or opt-in guard appears in the postinstall path before these configuration writes.
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-1249.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing create-chemx@26.9.16-1249. 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.