@vatio-ai/cli@0.89.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install hook, and the agent-related behavior inspected is invoked through ordinary CLI commands. Session sharing requires confirmation and authorization before sending the selected transcript to the configured Vatio service.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and has no npm install lifecycle hook.
- Running `vatio init` writes a local workspace note; the note provides Vatio workflow guidance.
- The skills hint runs after selected report commands, skips CI or an opt-out, and checks Vatio’s skills version registry.
- Session sharing asks for confirmation, requires authorization, and posts the chosen transcript to the configured Vatio service.
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.89.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.89.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.