chemx@26.9.20-390
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 active postinstall hook that mutates consumer AI-agent configuration without a consent check. This is a concrete install-time control-surface change, so the package should be blocked.
Decision evidence
public snapshot- package.json defines a postinstall hook that runs cli/postinstall.js.
- The hook calls installAllMcpConfigs for the consumer project during installation.
- That installer writes MCP configuration into the project’s .cursor/mcp.json and .vscode/mcp.json without a consent check.
- The added MCP entry can launch chemx via npx when an agent uses the configured server.
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 chemx@26.9.20-390.
See all versions of chemx for other recorded verdicts.
- Avoid installing chemx@26.9.20-390. 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.