@vatio-ai/cli@0.125.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged agent-control finding resolves to reminder-state writes and an AGENTS.md note written by the explicit init command. Runtime telemetry is disclosed, limited to command outcome metadata, and can be disabled; credentials are sent to the configured Vatio API.
Decision evidence
public snapshot- The package exposes a CLI entry point at bin/vatio.mjs.
- Runtime telemetry is disclosed to users and can be disabled with VATIO_TELEMETRY=0.
- Run reports contain the command label, exit code, duration, skill status and error description; they are sent to the configured Vatio API endpoint.
- The skills hint checks the Vatio skills registry and stores its check and display state under configHome, rather than modifying agent instructions.
- The AGENTS.md write is part of the explicitly invoked init command.
- The flagged skills-hint code writes reminder state files and prints a skills update hint; it does not write AI-agent instructions or settings.
- Credential-bearing requests use the configured Vatio base URL and workspace API path.
- The CLI’s ordinary telemetry notice says what is reported and gives an opt-out.
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.125.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.125.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.