@chemx/create-chemx@26.10.4-235
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall lifecycle hook unconditionally invokes configuration code that writes to consumer and, conditionally, user-level AI-agent settings without asking for consent. This supports blocking under the install-time agent control-surface policy; the source does not establish credential theft or an unrelated remote payload.
Decision evidence
public snapshot- The package defines a postinstall hook that calls cli/postinstall.js.
- The hook targets the consumer project and invokes the MCP configuration installer without a consent check.
- The installer writes MCP configuration into the consumer’s Cursor and VS Code settings, and adds helper scripts to its package.json.
- When an Antigravity configuration directory exists, the installer also writes a global MCP configuration and synchronizes agent schemas.
- The MCP entry points to this package’s own command, or to the ChemX command through npm exec, rather than an unrelated remote endpoint.
- The separate installer wizard presents explicit choices, but that prompt does not guard the postinstall path.
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.10.4-235.
See all versions of @chemx/create-chemx for other recorded verdicts.
- Avoid installing @chemx/create-chemx@26.10.4-235. 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.