@vatio-ai/cli@0.76.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 24d ago · by lpm-firewall-aiInspected the manifest, CLI entrypoint, required finding files, and relevant callers. The flagged agent-related behavior is tied to explicit commands, and the source does not establish a concrete attack surface.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and lists only yaml as a dependency; it declares no lifecycle script.
- The project note is written by the explicit init command, and existing notes mentioning Vatio are left alone.
- The skills hint reads installed plugin and project skill versions; its caller is an explicit CLI command.
- Session sharing is an explicit command and asks for confirmation before sending when --yes is absent.
- The CLI dispatches user-provided command arguments to explicit command handlers.
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 unpkgThe skills hint reads installed plugin and project skill versions; its caller is an explicit CLI command.
lib/skills-hint.mjsView on unpkg · L77Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.76.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.76.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.