@vibelet/cli@1.2.211
Cross-platform CLI for installing and running the Vibelet daemon
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe required agent-integration locations are executable PATH construction rather than configuration writes. Package metadata exposes a CLI without lifecycle hooks or a self-dependency chain.
Decision evidence
public snapshot- Package metadata exposes the Vibelet executable directly and contains no lifecycle-script section.
- Both indicated agent-related locations add Claude and Codex executable directories to a service PATH; they do not write agent configuration.
- The service PATH is used so the package daemon can locate child command-line tools.
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.211.
See all versions of @vibelet/cli for other recorded verdicts.
- Review the evidence and your use of @vibelet/cli@1.2.211 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.