@chemx/starter-kit@26.9.9-632
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an explicitly invoked remote installer, not an automatic lifecycle attack, but its unchecked server-controlled paths create a concrete arbitrary-write risk. The absence of install hooks and local payload execution supports a warning rather than a block.
Decision evidence
public snapshot- Its user-invoked CLI sends a license key and persistent device identifier to a remote service.
- The CLI writes every server-provided file path and content without validating that the path remains inside the chosen project directory.
- The scaffold command also adds a Cursor rules file to the new project.
- package.json has no preinstall, install, or postinstall hook.
- The executable is exposed only through explicit CLI commands.
- No credential harvesting beyond the supplied license key, shell payload execution, or automatic install-time execution was found.
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 @chemx/starter-kit@26.9.9-632.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chemx/starter-kit@26.9.9-632 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.