@chem-x/create-chemx@26.9.9-720
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package lacks install-time hooks, but its explicit scaffold and init flows trust remote file paths without confinement. That creates a meaningful supply-chain arbitrary-write risk requiring a warning.
Decision evidence
public snapshot- The create and init commands download a server-provided file map, then write each supplied path and content without validating that it remains inside the selected directory.
- The command sends a supplied license key and a persistent device identifier to the package service.
- The CLI creates a home-directory configuration folder during module initialization.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The network download and project writes occur only after a user invokes a CLI scaffold or init command and provides a license key.
- The browser-launching child-process calls are limited to explicit purchase links; no shell command string or evaluator is present.
Source & flagged code
5 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
cli/index.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @chem-x/create-chemx@26.9.9-720.
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.9-720 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.