@chemx/starter-kit@26.9.17-309
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package's automatic postinstall mutates consumer AI-agent configuration without a consent gate, establishing an active install-time control-surface change. This meets the blocking policy for unconsented postinstall mutation; the inspected evidence does not establish credential theft.
Decision evidence
public snapshot- package.json runs cli/postinstall.js automatically after installation.
- The postinstall uses the consumer install directory and calls installAllMcpConfigs without asking for consent.
- The installer writes MCP server configuration into project .cursor/mcp.json and .vscode/mcp.json.
- The configured server launches the local CLI or runs npx -y chemx mcp; an existing Gemini config also receives a global MCP entry.
- The targeted agent configuration locations contain MCP installer behavior and tests confirming the Cursor entry is created.
- The package self-install case is skipped, and errors are caught without failing installation.
- The integration configures a named Chemical X MCP server; source evidence does not show credential collection or exfiltration.
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 source references child process execution.
cli/audit-preflight-git.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @chemx/starter-kit@26.9.17-309.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Avoid installing @chemx/starter-kit@26.9.17-309. 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.