@vatio-ai/cli@0.126.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged agent-instruction write occurs only as part of the user-run `vatio init` workspace setup command. Skills hints are command-triggered, and the default telemetry is disclosed, opt-out capable, and sent to the configured Vatio API; the reviewed source shows no malicious behavior.
Decision evidence
public snapshot- The manifest exposes a `vatio` CLI entry point and declares no package main or exports.
- `vatio init` is an explicit CLI command; it creates the workspace manifest and adds a Vatio-specific note to that directory’s `AGENTS.md`.
- The skills hint runs after `vatio test list` output or saving, and can be disabled with `VATIO_NO_SKILLS_HINT`; it records hint state under Vatio’s config home.
- Runtime telemetry is described to users, has `VATIO_TELEMETRY=0` and `DO_NOT_TRACK=1` opt-outs, and reports command outcomes to the configured Vatio API endpoint.
- Telemetry is enabled by default and may include an error message when a command fails.
- `vatio init` writes agent instructions in the workspace directory, but only when that explicit command is run.
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.126.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.126.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.