@chem-x/starter-kit@26.9.21-227
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package automatically writes agent server configuration during npm postinstall without a consent guard, which meets the policy for blocking unconsented lifecycle mutation of an AI-agent control surface. The evidence establishes control-surface mutation, not credential theft or a malicious network endpoint.
Decision evidence
public snapshot- package.json runs cli/postinstall.js as an npm postinstall hook.
- The hook invokes installAllMcpConfigs for the consumer directory without a consent check.
- The invoked installer registers an MCP server in project agent settings and may also update the user's Antigravity configuration.
- When no local starter-kit CLI is found, the registered server runs npx -y chemx mcp.
- The installer also contains code that adds behavior-bearing directives to AGENTS.md, but that helper is not called by this postinstall hook.
- The configuration targets this package's MCP server, and the Antigravity write is conditional on an existing configuration directory.
- The AGENTS.md directive helper is used by a separate installer flow, not by the postinstall 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 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.21-227.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Avoid installing @chem-x/starter-kit@26.9.21-227. 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.