@vatio-ai/cli@0.84.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no install hooks or concrete attack behavior. Agent-related file changes are tied to explicit CLI commands, and session upload is gated by user confirmation or an explicit yes.
Decision evidence
public snapshot- package.json declares the CLI entrypoint and dependency but no install lifecycle hook.
- The CLI routes `init` to workspace setup, which writes a Vatio note to AGENTS.md only when that command runs.
- The skills hint reads installed skill metadata and writes its own hint cache; it is called from an explicit improve command.
- Session sharing is an explicit CLI command; it offers a save-to-file path and requires confirmation or an explicit yes before sending.
- The session upload sends a bearer token to the configured API base URL; the source sets Vatio as the default and allows an explicit environment or config override.
- Other indicated CLI locations show normal command reporting and a retry limited to a claimed-trial error; the child process helper runs fixed git arguments.
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.84.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.84.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.