@chem-x/create-chemx@26.9.28-276
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall hook automatically mutates project agent configuration and can also mutate an existing global Antigravity configuration, registering a package-controlled MCP server without consent. This meets the policy for blocking install-time AI-agent control-surface hijacking.
Decision evidence
public snapshot- The package defines a postinstall hook that runs cli/postinstall.js.
- Postinstall targets the consumer directory and automatically calls the MCP installer without a consent check.
- The installer writes a Chemical X MCP server entry into project Cursor configuration.
- If the Antigravity configuration directory exists, the installer writes its global MCP configuration and synchronizes agent schemas.
- The registered server runs this package’s MCP command, or falls back to npm exec for chemx.
- The explicit setup code also writes agent guidance to AGENTS.md; the wizard writes AGENTS.md and .cursorrules when pillars are selected.
- The postinstall skips when the target is the package’s own development directory.
- The Antigravity global configuration write is conditional on its configuration directory already existing.
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 @chem-x/create-chemx@26.9.28-276.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.28-276. 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.