@chemx/create-chemx@26.9.11-481
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo lifecycle execution or confirmed credential theft is present, but the explicit scaffold path is an unvalidated remote payload carrier with potential arbitrary file writes. This warrants a warning rather than a publish block.
Decision evidence
public snapshot- The create and init commands download a server-supplied file map and write every returned path without path validation.
- The downloaded content is controlled by a remote endpoint and receives the supplied license key and a persistent device identifier.
- Importing the CLI's license module creates a home-directory configuration folder.
- package.json has no preinstall, install, or postinstall hook.
- Remote download and project writes occur only after an explicit create or init command.
- GitHub token use is confined to the explicit audit-sharing feature.
Source & flagged code
5 flagged · loading sourceManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
cli/scaffold.jsView on unpkgThe create and init commands download a server-supplied file map and write every returned path without path validation.
cli/scaffold.jsView on unpkg · L37Findings
Affected versions and remediation
This report applies to @chemx/create-chemx@26.9.11-481.
See all versions of @chemx/create-chemx for other recorded verdicts.
- Review the evidence and your use of @chemx/create-chemx@26.9.11-481 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.