@vatio-ai/cli@0.117.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source shows disclosed, opt-out runtime telemetry sent to the configured Vatio service, with error descriptions that can include stack frames or local path details. This is a telemetry concern, not clear malicious behavior; the flagged agent-file write is limited to the explicit `vatio init` command.
Decision evidence
public snapshot- Each CLI command automatically reports its command label, exit code and, on failure, an error description.
- The report POST includes the workspace and uses the configured Vatio base URL; it may attach the saved token for authentication.
- Some error descriptions include CLI error messages or stack traces, which can contain local path details.
- The CLI discloses command-outcome telemetry and provides VATIO_TELEMETRY=0 and DO_NOT_TRACK=1 opt-outs.
- AGENTS.md is written by the explicit `vatio init` command, rather than automatically at install or import.
- The manifest has no lifecycle scripts; the package runs as a CLI entry point.
- Telemetry is disclosed, can be disabled, and reports to the configured Vatio service.
- Session sharing requires explicit confirmation or --yes; it does not send transcripts automatically.
- The skills hint reads agent configuration and writes only CLI state under configHome; it does not modify agent instructions.
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.117.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.117.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.