@vatio-ai/cli@0.82.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no install lifecycle hooks, and the flagged agent configuration write is limited to explicit `vatio init`. Transcript sharing requires `--yes` or terminal confirmation and sends to the configured Vatio API, so the scanner findings do not establish an attack.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and has no install lifecycle script.
- The project AGENTS.md note is written only by the explicit init command.
- The skills hint checks agent installation metadata and stores its display state under Vatio's config home when called from the flags command.
- Session sharing requires --yes in noninteractive use or terminal confirmation before sending.
- The transcript is sent to the configured Vatio API; the default base URL is vatio.ai.
- The entry point dispatches requested commands; the update handoff validates a release version, and the shared Git helper uses fixed arguments.
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.82.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.82.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.