@vibelet/cli@1.2.215
Cross-platform CLI for installing and running the Vibelet daemon
AI Security Review
scanned 23d ago · by lpm-firewall-aiInspected source supports guarded, user-invoked agent configuration capability, which the supplied policy classifies as warning-worthy. No concrete block-eligible malicious chain was established.
Decision evidence
public snapshot- The CLI explicitly launches managed agent terminals, where guarded Claude integration supplies generated hook settings.
- Claude settings are created in a temporary directory; hook events are forwarded to the local daemon at 127.0.0.1.
- The daemon generates SessionStart and PreToolUse command hooks and supplies their settings when hook credentials and approval conditions permit.
- package.json declares the CLI entrypoint without npm lifecycle hooks or a runtime self-dependency.
- The flagged inventory worker location adds agent executable directories to PATH.
- No confirmed covert exfiltration or install-time agent configuration mutation was established.
- Terminal hook setup requires a local control token and preserves explicitly supplied Claude settings.
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.215.
See all versions of @vibelet/cli for other recorded verdicts.
- Review the evidence and your use of @vibelet/cli@1.2.215 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.