@vatio-ai/cli@0.131.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package discloses runtime telemetry and offers opt-outs, but its failure reports can carry identifying details such as paths or user-specific text to Vatio’s service. This is suspicious telemetry, not clear malicious exfiltration.
Decision evidence
public snapshot- The CLI reports run telemetry after each command, unless telemetry is disabled.
- Run reports include the command outcome, error details, and workspace identifier, sent to Vatio’s CLI events endpoint.
- Failure details can include an error message or stack trace; the code replaces the home directory but may leave other local paths or user-specific text.
- The CLI discloses telemetry and provides VATIO_TELEMETRY=0 and DO_NOT_TRACK=1 opt-outs.
- The telemetry comments say arguments, file contents, and secrets are not sent; the code also strips the home directory from error details.
Source & flagged code
9 flaggedManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
lib/skills-hint.mjsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.131.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.131.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.