@chem-x/create-chemx@26.9.17-309
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package's postinstall hook automatically writes agent configuration into the consumer project without consent. This is a concrete unconsented install-time mutation of an AI-agent control surface, so the package should be blocked.
Decision evidence
public snapshot- package.json runs cli/postinstall.js from the postinstall lifecycle hook.
- The postinstall entrypoint automatically calls installAllMcpConfigs for the consumer directory without a consent check.
- The MCP installer writes a Chemical X server entry to the consumer project's .cursor/mcp.json.
- The postinstall-triggered project configuration write creates an agent control surface during installation.
Source & flagged code
10 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 @chem-x/create-chemx@26.9.17-309.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.17-309. 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.