@vatio-ai/cli@0.86.1
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the agent-file setup and transcript upload are tied to explicit CLI commands. Runtime telemetry is opt-out, reports command outcome and error metadata to the configured API URL, and defaults to Vatio; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json exposes the CLI through bin/vatio.mjs and declares no install lifecycle hook.
- The AGENTS.md note is created by the explicit init command in the current directory, and an existing note that mentions Vatio is left unchanged.
- Skills hints inspect agent installation metadata and show suggestions after user-invoked improve commands; they skip in CI or when disabled and keep their check state in Vatio configuration.
- Transcript upload is reachable through the explicit share-session command; without --yes it requires an affirmative terminal response, and the send uses the configured service URL.
- Run telemetry is sent only when telemetry is enabled and a command ran; it reports the command, exit status, and error metadata to the configured API URL. The default URL is Vatio.
- The inspected child-process helper invokes git with fixed arguments to read repository metadata.
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.86.1.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.86.1 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.