@vatio-ai/cli@0.123.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe routed agent-configuration write is scoped to the current directory and occurs only in vatio init. Runtime telemetry is disclosed, opt-out is supported, and its reports go to the configured Vatio service; the skills hint only recommends an install command.
Decision evidence
public snapshot- The manifest exposes the CLI through bin/vatio.mjs.
- The skills hint prints an optional npx install suggestion; it does not install the skills itself.
- The AGENTS.md write is part of the explicit vatio init command and targets the current workspace directory.
- Runtime telemetry is disclosed, can be disabled, and reports command outcomes to the configured Vatio service.
- The telemetry payload contains command, exit code, duration, installed-skill version and error details.
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 unpkgThe skills hint prints an optional npx install suggestion; it does not install the skills itself.
lib/skills-hint.mjsView on unpkg · L48Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.123.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.123.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.