@vibelet/cli@1.2.184
Cross-platform CLI for installing and running the Vibelet daemon
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not an install-hook attack because the manifest has no lifecycle scripts. The agent-session access, trust-state mutation, remote pairing, and persistence warrant a warning-level block decision rather than clean classification.
Decision evidence
public snapshot- The obfuscated daemon enumerates Codex session and archived-session directories.
- The daemon writes project records that mark trust dialogs and onboarding as accepted.
- The CLI enables remote access by default and offers Claude and Codex app takeover.
- It installs a persistent user service or detached daemon after an explicit CLI start.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The executable is a bin command, so the daemon path requires an explicit user invocation.
- The visible detached network check targets the npm registry for version metadata.
Source & flagged code
10 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.184.
See all versions of @vibelet/cli for other recorded verdicts.
- Review the evidence and your use of @vibelet/cli@1.2.184 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.