@vatio-ai/cli@0.128.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged agent-instruction write is performed by the explicit `vatio init` command. Runtime telemetry is disclosed and has an opt-out; credentialed requests use the configured Vatio API, and sharing a session requires consent.
Decision evidence
public snapshot- The AI-agent instruction file is written only by the explicit `vatio init` command.
- Runtime usage reporting is disclosed and can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1.
- Usage reports send command, exit status, duration, installed skill version and error details to the configured Vatio API.
- Session sharing requires confirmation or an explicit --yes flag; noninteractive runs stop without sending.
- The CLI makes network requests to Vatio and the npm registry during normal commands.
- The explicit init command may append a Vatio section to AGENTS.md.
Source & flagged code
11 flaggedManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
lib/skills-hint.mjsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.128.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.128.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.