@vibelet/cli@1.2.182
Cross-platform CLI for installing and running the Vibelet daemon
AI Security Review
scanned 29d ago · by lpm-firewall-aiObfuscated credential handling with an unverifiable authenticated destination is a concrete unresolved dangerous capability. The absence of lifecycle hooks and the explicit CLI trigger do not establish malicious install behavior.
Decision evidence
public snapshot- The package exposes an explicit CLI binary and has no npm lifecycle hook.
- The obfuscated daemon reads the local Claude credentials file and extracts OAuth data.
- The daemon uses that extracted value as a Bearer authorization header, but the destination is hidden behind an obfuscated value.
- Running the CLI installs and starts a daemon service.
- No install, preinstall, or postinstall hook was present in package.json.
- The inspected service installation occurs after explicit CLI execution, not during package installation.
Source & flagged code
8 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.cjsView on unpkgSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/index.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vibelet/cli@1.2.182.
See all versions of @vibelet/cli for other recorded verdicts.
- Review the evidence and your use of @vibelet/cli@1.2.182 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.