@vatio-ai/cli@0.133.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged agent configuration write is confined to the explicit vatio init command. Runtime telemetry is disclosed with an opt-out, and transcript sharing requires explicit user action; no credential theft or unrelated automatic action was found.
Decision evidence
public snapshot- The manifest exposes a CLI executable and declares no lifecycle scripts.
- Runtime telemetry is disclosed, excludes arguments, file contents and secrets, and can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1.
- The AGENTS.md write is part of the explicit vatio init command, which also creates a workspace manifest.
- Session transcripts are sent only through the explicit share-session flow, which asks for confirmation unless --yes is supplied.
- The skills hint checks the npm registry for a version and stores local hint state; it does not install or modify agent skills.
- The CLI sends default runtime usage telemetry to Vatio, including command labels and error information.
- vatio init writes a Vatio section into the workspace’s AGENTS.md file.
Source & flagged code
8 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.133.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.133.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.