@chem-x/create-chemx@26.9.21-227
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 hook that writes agent MCP configuration in the consumer project without a consent guard. That verified lifecycle mutation establishes an unconsented agent control-surface write, so this warrants blocking under the install-control-surface policy.
Decision evidence
public snapshot- package.json runs cli/postinstall.js automatically after installation.
- The postinstall hook targets the consumer directory and calls installAllMcpConfigs without a user consent check.
- The MCP installer writes Cursor and VS Code project configuration to register the Chemical X server; it also registers Antigravity when its config directory exists.
- The server registration uses a local CLI when available or runs npx -y chemx mcp otherwise.
- The separate pillars wizard writes AGENTS.md and .cursorrules as an explicit setup path; it is not called by the postinstall hook.
- The MCP installer merges the server entry into existing configuration rather than replacing the whole configuration object.
- The postinstall hook skips installation when the target is the package's own directory.
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 contains a critical-looking secret pattern.
cli/errors/errors.spec.jsView on unpkg · L27Findings
Affected versions and remediation
This report applies to @chem-x/create-chemx@26.9.21-227.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.21-227. 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.