@chem-x/starter-kit@26.9.20-228
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic postinstall changes agent configuration without an interactive consent step, creating a concrete first-party agent extension lifecycle risk. The inspected behavior registers the package’s own MCP server and does not establish a broader control hijack or other malicious attack.
Decision evidence
public snapshot- The package runs a postinstall script that automatically registers its MCP server in consumer agent configurations.
- The installer writes project-level Cursor MCP configuration, and it also targets VS Code and an existing Antigravity configuration.
- A separate installer function can append behavior-bearing directives to an existing AGENTS.md; this is not called by the inspected postinstall path.
- The configured MCP server is the package’s own Chemical X service, making this first-party agent setup rather than evidence of a separate attack.
- The Antigravity global configuration is only changed when its configuration directory already exists.
Source & flagged code
12 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/starter-kit@26.9.20-228.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chem-x/starter-kit@26.9.20-228 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.