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 malicious install-hook behavior because there are no lifecycle hooks and activation requires an explicit CLI command. It remains suspicious because unvalidated server-supplied paths can write outside the chosen project directory.
Decision evidence
public snapshot- The explicit init and scaffold commands write every server-supplied filename without restricting it to the selected directory.
- The CLI sends a supplied license key and persistent device identifier to the package service.
- The scaffold command creates a Cursor rules file in the newly requested project.
- package.json has no preinstall, install, or postinstall hook.
- All file-writing and network behavior is reached through an explicitly invoked CLI command.
- No local secret harvesting, hidden execution, self-dependency, or destructive command was found.
- The audit command only reads source files and reports line counts.
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 · L6Findings
Affected versions and remediation
This report applies to chemx@26.9.9-632.
See all versions of chemx for other recorded verdicts.
- Review the evidence and your use of 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.