create-chemx@26.9.26-253
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest-triggered postinstall calls an installer that writes agent MCP configuration into the consumer project without a consent guard. This is an unconsented install-time AI-agent control-surface mutation, so it warrants blocking.
Decision evidence
public snapshot- The package manifest runs a postinstall script that invokes the package’s installer.
- The postinstall script targets the install-time project directory and calls the MCP configuration installer without a consent check.
- That installer writes MCP server configuration into the project’s Cursor and VS Code configuration files, using a local package command or an npm execution fallback.
- The installer also has code to append agent directives to AGENTS.md; a separate wizard writes AGENTS.md and .cursorrules when pillars are selected.
- The installer test confirms that project MCP configuration and helper scripts are added to a consumer package.
- The Antigravity global configuration is changed only when its configuration directory already exists.
- The separate pillars wizard writes agent files only when pillars are selected and the operation is not a dry run.
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.26-253.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing create-chemx@26.9.26-253. 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.