@chem-x/create-chemx@26.9.20-369
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package’s automatic postinstall path mutates project and user AI-agent control configuration without consent. This meets the policy for blocking unconsented install-time agent control-surface mutation.
Decision evidence
public snapshot- package.json runs a postinstall script that calls the MCP installer for the consumer directory.
- The postinstall path calls installAllMcpConfigs without a consent check.
- The MCP installer writes server configuration into consumer .cursor and .vscode settings and into an existing global Antigravity configuration.
- The installed server entry launches the Chemical X MCP server through a local CLI or npx.
- The installer specification confirms that the consumer IDE configuration is created.
- The separate guardrail wizard presents configuration choices and offers cancellation.
- The scaffold copies AGENTS.md only when the user runs scaffolding and the destination file is absent.
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.20-369.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.20-369. 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.