@vatio-ai/cli@0.113.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged agent-related write adds a project-specific Vatio note only during `vatio init`. Runtime telemetry is disclosed and can be disabled, while transcript sharing requires confirmation; the npm request retrieves skills-version metadata.
Decision evidence
public snapshot- The manifest exposes a Vatio CLI entry point.
- Only the explicit `vatio init` command writes a project `AGENTS.md` note that describes Vatio workflows.
- Session transcripts are sent only after `--yes` or interactive confirmation.
- The CLI discloses runtime telemetry and provides `VATIO_TELEMETRY=0` and `DO_NOT_TRACK=1` opt-outs; events go to the configured Vatio API.
- The skills hint checks the npm registry for the latest skills version and caches version-check state.
- Runtime telemetry is enabled by default and includes command outcomes and error details.
- Improve-related commands may make a request to the npm registry and write hint state under the Vatio config directory.
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.113.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.113.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.