@yhong91/vibetime@0.1.37
vibetime CLI — install AI-agent hooks (Claude Code, Codex, OpenCode, Pi) and report activity to vibetime.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is an explicit-user-command agent-control and telemetry capability, not an unconsented npm lifecycle attack. The hard-coded non-TLS endpoint and broad agent-history collection justify a warning.
Decision evidence
public snapshot- bin/vibetime.mjs explicitly installs hooks/plugins into Codex, Claude, OpenCode, and Pi configs.
- Installed hooks launch `vibetime hook`, which starts a detached local sync runner.
- Backfill reads agent session/history files and POSTs rollups to a hard-coded HTTP IP endpoint.
- Uploaded rollups include project, tool names, display file paths, machine hostname, and token-backed headers.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Config mutation requires the explicit `vibetime install` command; no import-time installation exists.
- The npm install call is only reachable through the explicit `vibetime upgrade` command.
- Source contains no remote-code loader, eval, credential harvesting, or destructive filesystem behavior.
Source & flagged code
4 flagged · loading sourcePackage source invokes a package manager install command at runtime.
bin/vibetime.mjsView on unpkg · L11478Findings
Affected versions and remediation
This report applies to @yhong91/vibetime@0.1.37.
See all versions of @yhong91/vibetime for other recorded verdicts.
- Review the evidence and your use of @yhong91/vibetime@0.1.37 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.