@vatio-ai/cli@0.100.3
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no malicious behavior. The agent-related writes occur through explicit CLI commands, transcript sharing has a consent boundary, and the network behavior is product update, skills-version, or telemetry traffic.
Decision evidence
public snapshot- package.json declares a CLI entry point and the yaml dependency, with no package install hook; the inspected dependency source implements YAML parsing and stringifying.
- The agent-related project write is called from the explicit `vatio init` command and adds a static Vatio workflow note to `AGENTS.md`.
- The skills hint is called after `vatio flags` output, skips CI or an environment opt-out, and records display timing under the Vatio config home.
- `share-session` is an explicit CLI command. Without `--yes`, it asks for confirmation or refuses noninteractive sending; the transcript request uses the configured Vatio base URL.
- Run telemetry sends command, exit status, and error information to the configured CLI events endpoint when enabled; the source provides telemetry opt-outs.
- `askSecret` is described as masking typed or pasted secrets to keep them out of shell history and terminal scrollback.
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.100.3.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.100.3 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.