@vatio-ai/cli@0.116.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source matches a Vatio workspace CLI: its flagged agent-file update is tied to explicit initialization, and the skills hint only checks for installed skills and caches its notice state. Runtime telemetry is disclosed and has an opt-out; no concrete malicious behavior was found.
Decision evidence
public snapshot- The manifest exposes a CLI binary and has no install lifecycle scripts.
- Runtime telemetry is disclosed, can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1, and reports command, exit status, and error details.
- The skills hint checks the official npm registry for a version and stores its own hint state; it is called from explicit CLI workflows.
- The AGENTS.md write occurs during `vatio init` in the current project.
- No automatic credential theft, unrelated collection, or concealed code execution was identified.
- The new visitor token is included in an eval request only when an identity was supplied to that 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.116.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.116.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.