@chemx/starter-kit@26.9.11-631
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo automatic lifecycle execution or self-dependency chain exists. However, explicit use of the CLI downloads unauthenticated-by-integrity content and writes unchecked server-selected paths, creating a concrete supply-chain risk.
Decision evidence
public snapshot- The scaffold fetches a server-supplied file map and trusts it as the installation payload.
- Returned file paths are joined and written without path validation, allowing traversal outside the chosen target directory.
- The scaffold also creates a Cursor rules file containing agent directives.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Scaffolding and in-repository installation require an explicit CLI command and a supplied license key.
- GitHub-token network use is reached through the explicit audit sharing flow.
Source & flagged code
5 flagged · loading sourcePackage source references child process execution.
cli/navigator-share.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @chemx/starter-kit@26.9.11-631.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chemx/starter-kit@26.9.11-631 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.