@chem-x/create-chemx@26.9.20-408
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic postinstall mutates project and potentially global AI-agent control configuration to register an executable MCP server without asking the user. This meets the policy for blocking unconsented install-time agent control-surface mutation; the inspected code does not establish credential theft or an install-time network request.
Decision evidence
public snapshot- `package.json` defines a `postinstall` hook that runs `cli/postinstall.js`.
- The postinstall handler targets the consumer’s working directory and calls `installAllMcpConfigs` without a consent check.
- That installer writes MCP configuration into the consumer’s `.cursor/mcp.json` and `.vscode/mcp.json` files, registering the `chemical-x` server.
- When Antigravity’s config directory exists, the same installer also writes a global MCP entry and synchronizes agent schemas and instructions.
- The generated MCP command can fall back to `npx -y chemx mcp`, adding an executable agent integration during package installation.
- The package’s interactive installer presents MCP setup as a selectable option; that is separate from the automatic postinstall path.
- The inspected installer configures MCP command entries; this evidence does not establish credential theft or an install-time network request.
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/create-chemx@26.9.20-408.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.20-408. 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.