@rubytech/create-maxy-code@0.1.568
Install Maxy — AI for Productive People
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not malicious under the install-time policy because npm installation has no consumer lifecycle hook and the risky operations require an explicit CLI invocation. The CLI nevertheless bypasses Claude onboarding/trust prompts and provisions plugins, so it warrants a warning.
Decision evidence
public snapshot- dist/index.js runs a broad system installer from its CLI entrypoint.
- It writes $HOME/.maxy-code/.claude/.claude.json with onboarding complete and HOME workspace trust enabled.
- It installs shipped and external Claude plugins at user scope.
- It downloads and executes vendor installers, including curl|sh paths.
- package.json has no preinstall, install, or postinstall hook; prepublishOnly is not consumer install-time.
- The behavior is activated by the create-maxy-code bin, an explicit user command.
- Claude configuration is isolated under $HOME/.maxy-code/.claude rather than the default global Claude directory.
- Reviewed installer paths show product deployment and setup, not credential collection or covert exfiltration.
Source & flagged code
20 flagged · loading sourcePackage contains a possible secret pattern.
payload/platform/scripts/smoke-boot-services.shView on unpkg · L349A single source file combines environment access, network access, and code or shell execution with blocking evidence.
dist/index.jsView on unpkg · L142Findings
Affected versions and remediation
This report applies to @rubytech/create-maxy-code@0.1.568.
See all versions of @rubytech/create-maxy-code for other recorded verdicts.
- Review the evidence and your use of @rubytech/create-maxy-code@0.1.568 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.