create-chemx@26.9.20-228
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 installs first-party MCP configuration into consumer agent surfaces. This is a real lifecycle risk, but the inspected source supports a warning rather than a malicious block.
Decision evidence
public snapshot- The package manifest runs cli/postinstall.js automatically after installation.
- The postinstall handler targets the consumer directory and invokes installAllMcpConfigs without a consent prompt.
- The installer creates or updates project-level Cursor and VS Code MCP configuration files.
- The MCP setup registers Chemical X as a server; this is package-owned agent integration rather than evidence of an unrelated payload.
- A source test confirms the installer creates these configuration files and adds package scripts.
- The postinstall setup is a first-party Chemical X MCP integration, which fits a guarded lifecycle warning rather than a confirmed malicious attack.
- The reviewed installer code does not show credential collection or exfiltration.
Source & flagged code
12 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.20-228.
See all versions of create-chemx for other recorded verdicts.
- Review the evidence and your use of create-chemx@26.9.20-228 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.