create-chemx@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 not an install-time attack: the manifest has no lifecycle hook and execution requires a CLI command. It warrants a warning because the package downloads opaque remote content and creates an AI-agent instruction file in the consumer project.
Decision evidence
public snapshot- The explicit scaffold and init commands fetch a license-gated, server-supplied file map and write every returned entry into the selected project directory.
- The scaffold command creates a .cursorrules AI-agent instruction file in the new project.
- The CLI sends a supplied license key and persistent device identifier to the package service.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- All filesystem and network actions are reached only through the declared CLI commands.
- No eval, dynamic module loading, credential harvesting, or destructive deletion is present.
- Browser launches use fixed purchase URLs.
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 · L6Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
cli/index.jsView on unpkg · L6Manifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
cli/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to create-chemx@26.9.9-632.
See all versions of create-chemx for other recorded verdicts.
- Review the evidence and your use of create-chemx@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.