@vatio-ai/cli@0.112.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged agent-instruction write occurs only during the explicit init command. However, default runtime error telemetry can include stack details that may expose local paths, despite the notice saying file contents and secrets are not sent, so this merits a warning rather than a clean verdict.
Decision evidence
public snapshot- The CLI notice says it never sends file contents or secrets, but automatic error reporting includes the first six lines of unexpected error stacks, which can contain local paths or other machine details.
- The CLI reports command outcomes automatically after a command runs and after errors; telemetry can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1.
- Events are POSTed to the configured Vatio base URL at /api/developer/v1/cli/events and include the workspace identifier.
- The flagged AGENTS.md write is called only by the explicit vatio init command.
- The skills hint checks the official npm registry for the latest skills version and stores its cache under the Vatio config directory.
- Telemetry is disclosed on first use and has environment-variable opt-outs.
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.112.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.112.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.