@chem-x/create-chemx@26.9.16-1408
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource confirms an automatic postinstall that writes agent configuration in the consumer project and may also write global Antigravity configuration, without an install-time consent guard. This meets the policy for blocking unconsented lifecycle mutation of AI-agent control surfaces.
Decision evidence
public snapshot- package.json runs cli/postinstall.js from its postinstall hook.
- The postinstall targets the consumer project and calls installAllMcpConfigs without a consent prompt.
- The lifecycle call writes MCP configuration into consumer .cursor/mcp.json.
- The same installer writes to an existing global Antigravity configuration when its directory is present.
- When no local starter is found, the configured server runs npx -y chemx mcp.
- The separate installer can append agent-directed search rules to an existing AGENTS.md, but that path is not needed to establish the lifecycle behavior.
- The MCP server registration is package-aligned functionality and preserves existing MCP server entries.
- The AGENTS.md instruction mutation is in the separate installer flow, not the postinstall call 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.16-1408.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.16-1408. 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.