@chemx/create-chemx@26.9.20-369
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install lifecycle automatically writes MCP configuration for consumer AI editors without a consent gate. This is unconsented postinstall mutation of a foreign AI-agent control surface, so it meets the blocking policy.
Decision evidence
public snapshot- package.json defines a postinstall command that runs cli/postinstall.js.
- The postinstall handler targets the consumer directory and calls installAllMcpConfigs without a consent prompt.
- The MCP installer writes a Chemical X server configuration into the consumer's Cursor and VS Code MCP files.
- When no local starter is found, the configured server command uses npx to run chemx mcp.
- The scaffold writes into a newly selected project directory; that explicit creation flow does not guard the automatic postinstall configuration writes.
- The installer merges the Chemical X server entry into existing MCP JSON rather than replacing the whole configuration.
- The MCP server command runs the package's own MCP CLI or the chemx package, consistent with the product's stated integration.
Source & flagged code
11 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 contains a critical-looking secret pattern.
cli/errors/errors.spec.jsView on unpkg · L27Findings
Affected versions and remediation
This report applies to @chemx/create-chemx@26.9.20-369.
See all versions of @chemx/create-chemx for other recorded verdicts.
- Avoid installing @chemx/create-chemx@26.9.20-369. 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.