@vibelet/cli@1.2.210
Cross-platform CLI for installing and running the Vibelet daemon
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe package is a user-invoked daemon CLI with no registry lifecycle scripts. The agent-integration hits only append existing Claude and Codex bin directories to PATH for child processes.
Decision evidence
public snapshot- package.json exposes only the vibelet bin at dist/vibelet.mjs and has no preinstall, install, or postinstall hook and no dependency on itself.
- dist/vibelet.mjs runs as the user CLI. The flagged .claude and .codex paths are directories added to PATH so daemon-spawned claude and codex wrappers can find node, not writes to agent config.
- The same PATH construction appears in obfuscated dist/index.cjs, which the CLI starts as the daemon entry rather than an npm install hook.
- dist/index.cjs and dist/inventory-scan-worker.cjs are obfuscated, so not every string is readable.
- When the user runs the CLI it can install a per-user daemon and a Cloudflare quick tunnel, which is the stated product behavior.
Source & flagged code
10 flagged · loading sourceSource downloads or fetches remote code and executes it.
dist/vibelet.mjsView on unpkg · L20A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/vibelet.mjsView on unpkg · L20Findings
Affected versions and remediation
This report applies to @vibelet/cli@1.2.210.
See all versions of @vibelet/cli for other recorded verdicts.
- Review the evidence and your use of @vibelet/cli@1.2.210 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.