@chemx/starter-kit@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 attack is present, but the explicit scaffolder trusts remote file paths and mutates an AI-agent control file. This warrants a warning rather than a publish block.
Decision evidence
public snapshot- The executable create and init commands invoke the scaffolder.
- The scaffolder writes every server-returned file path without validating that it stays inside the selected project directory.
- The create command adds a .cursorrules file containing agent instructions.
- The license request sends the entered license key and a persistent device ID to chemicalx.xophz.com.
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- The write and network paths require an explicit CLI create or init action.
- No self-dependency, credential harvesting beyond the supplied license key, or hidden command execution was found.
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 unpkgFindings
Affected versions and remediation
This report applies to @chemx/starter-kit@26.9.11-362.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chemx/starter-kit@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.