@vatio-ai/cli@0.120.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged agent-instruction write is confined to the current workspace and occurs during the user-invoked `vatio init` command. Runtime telemetry is disclosed, has an opt-out, and targets the configured Vatio service; the skills hint checks the official npm registry for the Vatio skills version.
Decision evidence
public snapshot- The manifest exposes a CLI binary and has no install lifecycle scripts.
- The `AGENTS.md` write is part of the explicit `vatio init` command, which also creates the workspace manifest.
- Runtime telemetry is disclosed to users, can be disabled with `VATIO_TELEMETRY=0`, and posts command outcome data to the configured Vatio base URL.
- The skills hint fetches only the Vatio skills package version and records hint state in the CLI config directory.
- The CLI may send runtime telemetry while enabled, including a workspace identifier and error descriptions.
- `vatio init` writes behavior-bearing instructions into a workspace `AGENTS.md` file when explicitly invoked.
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.120.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.120.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.