@chem-x/create-chemx@26.9.26-253
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall hook automatically registers the package’s own MCP server in agent configuration, creating a real agent-extension lifecycle risk. The inspected behavior fits first-party package-owned setup, which warrants a warning rather than a malicious block.
Decision evidence
public snapshot- package.json runs cli/postinstall.js after installation; that hook invokes the MCP installer for the consumer directory.
- The installer adds the package’s Chemical X MCP server to project Cursor and VS Code configuration, and registers it in Antigravity’s global configuration when that configuration exists.
- The configured server invokes the Chemical X MCP command; the inspected code shows no credential forwarding or unrelated command target.
- The setup installs this package’s own MCP integration, a guarded first-party agent extension setup covered by the warning policy.
- The separately inspected agent steering writes are in the explicit pillars wizard, not the postinstall path.
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 @chem-x/create-chemx@26.9.26-253.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Review the evidence and your use of @chem-x/create-chemx@26.9.26-253 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.