@chem-x/create-chemx@26.10.4-1258
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection confirms an active postinstall hook that mutates consumer Cursor and VS Code MCP configuration without a consent guard. This meets the policy for blocking unconsented install-time AI-agent control-surface mutation.
Decision evidence
public snapshot- package.json runs cli/postinstall.js during postinstall.
- The postinstall hook targets npm's consumer directory and calls the MCP installer without a consent check.
- The installer writes a Chemical X MCP server entry to the consumer's Cursor configuration.
- The installer also writes a Chemical X MCP server entry to the consumer's VS Code configuration.
- A separate installer path adds agent directives to AGENTS.md.
- The pillars wizard generates AGENTS.md and .cursorrules from selected pillars.
- The package also exposes interactive setup paths for MCP configuration and agent directives; those paths do not guard the automatic postinstall behavior.
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.10.4-1258.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.10.4-1258. 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.