@vatio-ai/cli@0.72.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 25d ago · by lpm-firewall-aiSession sharing conditionally forwards the existing Vatio token to an unrestricted configured destination, which presents a concrete credential exposure risk even though the command requires user invocation and ordinarily asks for confirmation. The agent-related writes inspected are explicit setup or local hint state and do not establish a separate attack.
Decision evidence
public snapshot- `share-session` sends a Claude Code transcript and attaches the token returned by `resolveToken()` as a Bearer credential.
- The request destination comes from `VATIO_BASE_URL` or the configured `base_url`; the source shows no destination restriction.
- Transcript sending requires explicit `--yes` or an interactive affirmative response, and requires authorization.
- The package’s agent configuration write is performed by the explicit `init` command; the skills hint checks for existing skills and plugins.
- The skills hint’s state write records when the hint was shown; it does not install or alter agent configuration.
- The manifest exposes a CLI executable and declares no install lifecycle hooks.
- Session sharing is an explicit command with a confirmation gate unless the caller supplies `--yes`.
- The default service destination is Vatio’s `https://vatio.ai` endpoint.
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.72.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.72.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.