@vatio-ai/cli@0.114.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package sends disclosed, opt-out runtime telemetry to its own API, but error details can retain local project paths, which are identifying information. This warrants a warning for telemetry; no malicious credential theft or unrelated data transfer was identified.
Decision evidence
public snapshot- The CLI reports command outcomes and error details by default when telemetry is enabled.
- For unexpected errors, the reported message can include the first six stack lines; it replaces the home directory but may leave project paths.
- Telemetry is posted to the Vatio CLI events endpoint.
- A first-run notice describes the reporting, and VATIO_TELEMETRY=0 or DO_NOT_TRACK=1 disables it.
- The manifest has no lifecycle scripts, and the package is a Vatio workspace management CLI.
- Telemetry goes to the configured Vatio API and uses the saved Vatio token; no unrelated collector was identified.
- The AGENTS.md write occurs only during the explicit vatio init command.
- The transcript-sharing command asks for confirmation unless --yes is supplied and offers --save to inspect the transcript first.
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.114.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.114.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.