@vatio-ai/cli@0.96.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete attack behavior. Agent configuration changes are tied to explicit workspace initialization, and the reviewed network activity supports package update checks and Vatio CLI telemetry.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint, declares yaml as its runtime dependency, and has no lifecycle script.
- The agent configuration write runs during `vatio init` and adds a Vatio workspace workflow note to the project’s `AGENTS.md`.
- The skills hint runs from explicit improvement commands, checks skill versions, and caches results without installing or rewriting agent configuration.
- The required yaml dependency excerpts show parser, schema, composition, and serialization modules; no attack behavior was identified in the reviewed paths.
- Run telemetry reports CLI events to the configured Vatio API; the CLI displays a notice and provides an environment-variable opt-out.
- Update and skills checks request release-version metadata and cache it; no remote code execution or payload installation was found.
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.96.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.96.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.