@vatio-ai/cli@0.121.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged skill path only checks versions and prints a hint, while its state stays under Vatio’s config directory. Runtime telemetry is disclosed with an opt-out, and the project AGENTS.md write belongs to the explicit init command.
Decision evidence
public snapshot- The manifest exposes a command-line executable and declares no lifecycle scripts or library entry point.
- The skills hint checks the npm registry and stores its check and display state under configHome(), not in agent instructions or settings.
- Telemetry is disclosed and can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1.
- Command telemetry sends command, exit status, optional error details, and workspace to the configured Vatio API base URL.
- The AGENTS.md helper is part of the explicit vatio init flow.
- Error telemetry can include a shortened error stack, which may contain local project paths; the CLI notice describes command outcome reporting and provides 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 unpkgThe skills hint checks the npm registry and stores its check and display state under configHome(), not in agent instructions or settings.
lib/skills-hint.mjsView on unpkg · L132Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.121.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.121.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.