@chem-x/create-chemx@26.9.25-1337
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe active postinstall path mutates consumer editor MCP configuration without an observed consent gate. The inspected behavior supports a warning for first-party agent integration setup, not a publish block.
Decision evidence
public snapshot- The package postinstall hook runs cli/postinstall.js, which targets the consuming project and calls the MCP configuration installer.
- The installer creates or updates the consumer's .cursor/mcp.json and .vscode/mcp.json to register this package's MCP server.
- The separate pillars wizard writes AGENTS.md and .cursorrules only when explicitly invoked; this behavior is not the postinstall path.
- The observed setup registers this package's own MCP server; inspected source does not establish credential collection, exfiltration, or a remote payload.
- No user confirmation gate was found in the postinstall path before the MCP configuration writes.
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/create-chemx@26.9.25-1337.
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.25-1337 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.