@chem-x/starter-kit@26.9.13-383
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected CLI behaviors are invoked by the user and aligned with scaffolding, license validation, and audit publishing. The generated .cursorrules content is package-specific and is written only during scaffolding when the target file is absent.
Decision evidence
public snapshot- package.json exposes the CLI through bin entries and defines no lifecycle install hooks.
- cli/license.js sends a supplied license key and generated device ID to the package’s license service to validate the key and retrieve starter files.
- cli/scaffold.js writes a package-specific .cursorrules file only when the user runs the scaffolder and the target file is absent.
- cli/terminal.js launches a browser with a URL supplied by the CLI; the inspected path does not show arbitrary shell command construction.
- cli/navigator-share.js publishes audit content through the package’s GitHub Discussions publishing 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 @chem-x/starter-kit@26.9.13-383.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chem-x/starter-kit@26.9.13-383 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.