@chem-x/create-chemx@26.9.23-1269
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource confirms an unprompted postinstall setup of the package's own MCP server in agent configuration, which warrants a warning under the agent extension lifecycle policy. The inspected source does not establish broader control-surface abuse or a separate concrete attack.
Decision evidence
public snapshot- The package postinstall hook invokes an MCP configuration installer for the consumer project.
- The installer writes ChemX MCP server configuration into project-level Cursor and VS Code files without an interactive consent check.
- The installer also supports global Antigravity configuration when its config directory already exists; the observed behavior is first-party setup for this package.
- The separate installer and pillars wizard write AI-agent guidance files only through installer or wizard flows; the inspected wizard code supports dry-run and preset selection.
- The MCP configuration registers this package's own ChemX server; the inspected code does not show credential collection, unrelated remote payload execution, or destructive behavior.
- The scanner-flagged secret pattern is in a test file containing sample tokens used to check sanitization.
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.23-1269.
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.23-1269 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.