@chem-x/create-chemx@26.9.11-481
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe behavior is user-invoked and package-aligned, so it does not meet the install-hook malware boundary. However, unchecked server-controlled paths create a real unresolved remote file-write risk.
Decision evidence
public snapshot- Explicit scaffold and init commands fetch a remote starter kit and write every returned path beneath the chosen target without path containment checks.
- The scaffold command creates a Cursor rules file in the selected new project.
- GitHub identity lookup only invokes local gh and git commands as part of the optional audit-sharing feature.
- package.json has no preinstall, install, or postinstall hook.
- Remote fetching and project writes occur only after an explicit CLI create or init action.
- No secret harvesting, shell evaluation, self-dependency, or automatic exfiltration 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 unpkgExplicit scaffold and init commands fetch a remote starter kit and write every returned path beneath the chosen target without path containment checks.
cli/scaffold.jsFindings
Affected versions and remediation
This report applies to @chem-x/create-chemx@26.9.11-481.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Review the evidence and your use of @chem-x/create-chemx@26.9.11-481 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.