@vatio-ai/cli@0.94.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed agent-related writes occur only through explicit CLI flows and are limited to workspace documentation or CLI hint state. The scanner’s agent-configuration finding is explained by these package-aligned behaviors; no concrete attack surface was established.
Decision evidence
public snapshot- package.json exposes a CLI entry and declares no lifecycle hooks.
- `vatio init` explicitly writes workspace files and calls the helper that adds a local AGENTS.md note.
- The note writer creates or appends only to AGENTS.md in the selected workspace.
- The skills hint can be suppressed in CI or with an environment flag and stores display state in the CLI config home.
- The skills hint checks for existing Vatio skills and prints update instructions; it does not install or modify agent plugins.
- The skills hint is called from explicit CLI command flows.
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.94.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.94.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.