@vatio-ai/cli@0.109.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged AGENTS.md write is part of the explicit `vatio init` command and is limited to its workspace. The skills check contacts the npm registry for version information, while disclosed runtime telemetry has an opt-out and uses the configured Vatio API.
Decision evidence
public snapshot- The AGENTS.md write occurs in vatio init after it writes the workspace manifest, so it requires an explicit setup command.
- The skills hint is called from selected CLI commands and fetches only the latest @vatio-ai/skills version from the npm registry.
- Runtime telemetry is disclosed, excludes arguments, files and secrets, and can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1.
- Telemetry posts to the configured Vatio API base URL; the default is https://vatio.ai.
- The package has a CLI bin entry and no lifecycle script in its manifest.
- The skills hint writes reminder and version cache files under configHome(), not agent instructions or settings.
- Telemetry includes command and error details, but the package discloses this collection 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 is called from selected CLI commands and fetches only the latest @vatio-ai/skills version from the npm registry.
Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.109.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.109.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.