@vatio-ai/cli@0.118.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install hooks, and the inspected agent-instruction write occurs during an explicit project initialization command. Runtime telemetry is disclosed with an opt-out, while session transcripts require confirmation before sending.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and exposes the CLI through bin/vatio.mjs.
- The AGENTS.md note is written by vatio init in the target project directory.
- Sharing a session requires --yes or an interactive confirmation; the transcript is sent to the configured Vatio API.
- Runtime command telemetry is disclosed and can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1.
- The CLI makes network requests and writes local state during normal operation.
- vatio init adds project-level guidance to AGENTS.md.
Source & flagged code
6 flaggedManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
lib/skills-hint.mjsView on unpkgFindings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.118.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.118.0 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.