@vatio-ai/cli@0.101.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete attack behavior. The flagged agent configuration write is reachable through explicit `vatio init`, and the inspected YAML dependency source is parser and stringifier functionality.
Decision evidence
public snapshot- The package exposes a CLI entrypoint and depends on yaml; the inspected dependency source implements YAML parsing, composition and stringification, and its manifest has no install hook.
- The agent-facing AGENTS.md note is written by the explicit init command, which creates a workspace manifest; this is user-invoked workspace setup.
- The skills hint runs in explicit improve commands, checks skill versions, and stores its reminder state under the CLI config home.
- Run telemetry is disclosed and can be disabled; it sends command outcome metadata to the configured service base URL.
- Sharing a session transcript requires affirmative confirmation when the command has not been explicitly authorized.
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.101.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.101.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.