@chem-x/create-chemx@26.9.17-606
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package has an automatic postinstall path that mutates foreign AI-agent control configuration in the consumer environment without consent. This meets the policy for blocking an unconsented install-hook control-surface mutation.
Decision evidence
public snapshot- package.json defines a postinstall hook that runs cli/postinstall.js.
- The postinstall hook calls the MCP installer on the consumer project without a consent check.
- The installer writes MCP server configuration into project-level Cursor and VS Code control files, and may add a server to the user’s Gemini configuration.
- The MCP server definition launches the ChemX command through npx when no local copy is found.
- The MCP configuration registers this package’s own server command; source does not show credential collection or transmission in this install path.
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 @chem-x/create-chemx@26.9.17-606.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.17-606. 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.