@chem-x/starter-kit@26.10.8-344
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe postinstall hook performs unconsented changes to project and global AI-agent control configuration and enables the package's MCP capabilities. This is concrete installation-time control-surface abuse, so publication should be blocked.
Decision evidence
public snapshot- The package manifest runs cli/postinstall.js automatically after installation, and the script invokes the MCP installer for the consumer directory without an affirmative consent check.
- The installer merges and writes MCP server configuration into the consumer project's Cursor and VS Code config files.
- When Antigravity's global config directory exists, the installer writes its MCP server registration and synchronizes tool schemas and instructions under the user's home directory.
- Generated Antigravity instructions say the master tool avoids separate approval for each sub-operation, and the registered MCP tool exposes file read, patch, and write actions.
Source & flagged code
15 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/starter-kit@26.10.8-344.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Avoid installing @chem-x/starter-kit@26.10.8-344. 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.