@vibelet/cli@1.2.185
Cross-platform CLI for installing and running the Vibelet daemon
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo concrete install-hook abuse, secret theft, or destructive action was established. Deliberate daemon obfuscation combined with persistent execution leaves a material unresolved risk.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint that runs dist/vibelet.mjs.
- The packaged daemon in dist/index.cjs is deliberately obfuscated, preventing reliable static auditing of its behavior.
- A normal CLI run installs a user service configured to start at login and remain alive.
- The CLI launches a detached background process that contacts the npm registry for update checks.
- package.json contains no preinstall, install, or postinstall hook.
- Persistence is reached through the user-invoked CLI entrypoint rather than package installation.
- The visible CLI code identifies its persistent daemon and service files rather than hiding those writes.
Source & flagged code
8 flagged · loading sourceSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/index.cjsView on unpkg · L1Source contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/index.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vibelet/cli@1.2.185.
See all versions of @vibelet/cli for other recorded verdicts.
- Review the evidence and your use of @vibelet/cli@1.2.185 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.