@chem-x/starter-kit@26.9.20-390
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource confirms an npm postinstall trigger that automatically writes MCP server configuration into consumer-project AI-tool control files without a consent guard. This meets the block policy for unconsented install-time mutation of an AI-agent control surface.
Decision evidence
public snapshot- The package manifest runs a postinstall script.
- Postinstall targets the consuming project and calls the MCP installer without a consent check.
- The MCP installer writes a Chemical X server entry into the consumer’s Cursor MCP configuration; it also configures VS Code.
- If no local executable is found, the saved server command uses npx to invoke chemx mcp.
- A separate installer path can add instructions to AGENTS.md, and the scaffold path copies AGENTS.md during explicit scaffolding.
- The MCP installer test confirms it creates Cursor configuration.
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/starter-kit@26.9.20-390.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Avoid installing @chem-x/starter-kit@26.9.20-390. 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.