create-chemx@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-aiThere is no automatic npm lifecycle execution, but the explicit scaffold workflow trusts remote file paths and creates an AI-agent instruction file. That creates a meaningful supply-chain and agent-extension risk requiring a warning.
Decision evidence
public snapshot- The user-invoked scaffold downloads server-provided files and writes each response entry into the new project without path validation.
- Scaffolding also creates a .cursorrules AI-agent instruction file automatically.
- The CLI caches a supplied license key and a persistent device identifier in the user home directory.
- package.json contains no preinstall, install, or postinstall lifecycle hook.
- The writes and network download require an explicit create/scaffold command.
- Git hooks and GitHub workflow writes are behind an interactive installer choice.
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 create-chemx@26.9.11-631.
See all versions of create-chemx for other recorded verdicts.
- Review the evidence and your use of create-chemx@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.