@chem-x/starter-kit@26.9.26-253
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package's postinstall hook automatically writes behavior-bearing MCP entries into project-level Cursor and VS Code configuration without consent. This meets the policy for unconsented install-time mutation of a foreign AI-agent control surface.
Decision evidence
public snapshot- package.json runs cli/postinstall.js automatically after installation.
- The postinstall hook targets the consumer project and calls installAllMcpConfigs without a consent check.
- The installer creates or updates project-level Cursor and VS Code MCP configuration to register a Chemical X server.
- The registered server runs a local Chemical X CLI or falls back to npm exec, making the new agent configuration behavior-bearing.
- The package also exposes an interactive installer for MCP setup, but the automatic postinstall path bypasses that choice.
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.26-253.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Avoid installing @chem-x/starter-kit@26.9.26-253. 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.