create-chemx@26.9.17-1100
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package automatically mutates consumer Cursor and VS Code MCP configuration from its postinstall hook without asking for consent. This meets the policy for blocking unconsented install-time mutation of an AI-agent control surface.
Decision evidence
public snapshot- package.json runs cli/postinstall.js automatically during installation.
- The postinstall targets INIT_CWD or the current directory and calls installAllMcpConfigs without a consent prompt.
- The installer writes MCP configuration into consumer .cursor and .vscode directories, replacing the chemical-x server entry.
- When the package is present locally, the generated MCP configuration launches its CLI in MCP mode.
- The CLI also exposes an explicit MCP installation command; the package’s install hook nevertheless performs the configuration automatically.
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 create-chemx@26.9.17-1100.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing create-chemx@26.9.17-1100. 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.