create-chemx@26.9.11-362
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo automatic lifecycle behavior or confirmed credential exfiltration is present. However, the remote asset installer has a concrete path-traversal arbitrary-write risk during an explicit scaffold operation.
Decision evidence
public snapshot- The scaffold command downloads a server-provided file map and writes each supplied path without validating that it remains inside the target directory.
- The same explicit scaffold command creates a Cursor rules file in the newly created project.
- The package can persist a device identifier and supplied license key in the user's home configuration directory when its CLI is invoked.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Network download and project writes occur only after the user runs a scaffold command and provides a license key.
- Git hooks and CI workflow writes are behind an interactive, explicit install command.
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 scaffold command downloads a server-provided file map and writes each supplied path without validating that it remains inside the target directory.
cli/scaffold.jsView on unpkg · L37Findings
Affected versions and remediation
This report applies to create-chemx@26.9.11-362.
See all versions of create-chemx for other recorded verdicts.
- Review the evidence and your use of create-chemx@26.9.11-362 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.