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 behavior-bearing MCP configuration into consumer AI-agent surfaces without consent. This meets the package policy for blocking unconsented install-time control-surface mutation.
Decision evidence
public snapshot- package.json runs cli/postinstall.js during installation.
- The hook targets the consumer directory and calls installAllMcpConfigs without a consent check.
- The MCP installer writes project Cursor and VS Code server configurations and may register a global Antigravity server when its configuration directory exists.
- The registered server command can fall back to npx -y chemx mcp.
- The installer spec confirms that the project Cursor configuration contains a chemical-x MCP server.
- The separate installer and scaffold paths also modify agent guidance when invoked; those paths do not explain away the postinstall MCP configuration.
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 create-chemx@26.9.20-369.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing 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.