@chemx/starter-kit@26.9.20-1318
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest-triggered postinstall automatically writes behavior-bearing MCP configuration into consumer agent surfaces without consent. This is an active install-time control-surface mutation, so the package should be blocked.
Decision evidence
public snapshot- The manifest runs `cli/postinstall.js` as an npm postinstall hook.
- That hook targets the installing project and calls the MCP config installer without a consent check.
- The installer writes a Chemical X MCP server entry into the project’s Cursor and VS Code configs.
- The server command can fall back to `npx -y chemx mcp`, enabling those agent clients to run the package’s MCP server.
- The package also has a separate interactive wizard for agent steering files, but that does not gate the postinstall MCP configuration writes.
Source & flagged code
10 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 @chemx/starter-kit@26.9.20-1318.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Avoid installing @chemx/starter-kit@26.9.20-1318. 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.