create-chemx@26.9.21-432
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe active postinstall lifecycle writes MCP configuration for consumer AI tools without an opt-in prompt. The resulting gateway consolidates operations and is described as avoiding separate approval for each operation, so this meets the install-time AI-agent control-surface block rule.
Decision evidence
public snapshot- The package manifest runs cli/postinstall.js after installation.
- Postinstall calls the MCP installer for the consumer project without an interactive consent step.
- The MCP installer writes Cursor and VS Code MCP configuration and registers the package’s server.
- The MCP tool manifest says its single gateway avoids separate approval for each sub-operation.
- The installer also has agent-search and pillars configuration paths, but these are separate from the postinstall chain.
- The postinstall skips when installing inside the starter-kit itself.
- The Antigravity user-level configuration is only changed when its configuration directory already exists.
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 create-chemx@26.9.21-432.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing create-chemx@26.9.21-432. 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.