@vatio-ai/cli@0.122.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 5d ago · by lpm-firewall-aiThis is disclosed, opt-out runtime telemetry to the package's own service, but error stacks can contain identifying local paths. That makes the telemetry a warning-level privacy risk under the review rules.
Decision evidence
public snapshot- Run telemetry is enabled by default unless VATIO_TELEMETRY or DO_NOT_TRACK disables it.
- Failed runs include an error description in the telemetry event.
- For many errors, the description includes up to six lines of the error stack, which can contain local file paths.
- The event is posted to the configured Vatio API endpoint.
- The CLI announces its runtime telemetry and provides an opt-out.
- The source says it does not send command arguments, file contents, or secrets.
- The skill hint fetches a version from the npm registry and writes its cache under the Vatio config directory.
- The AGENTS.md write occurs only during the explicit init command.
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.122.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.122.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.