@vatio-ai/cli@0.103.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged agent-file write occurs through explicit `vatio init`. The inspected telemetry is opt-out and reports command metadata through the configured service; no concrete malicious behavior was established.
Decision evidence
public snapshot- package.json declares the CLI entrypoint and YAML dependency, with no lifecycle scripts.
- The AGENTS.md note is written during the explicit `vatio init` command; the skills hint checks installed versions and caches its display state.
- The required YAML dependency files implement parsing, composition, and stringification; its manifest has no install scripts.
- Telemetry is disabled by supported environment settings and otherwise reports command metadata and errors through the configured Vatio service.
- The required CLI source paths identify command modules and local configuration handling; no attack behavior was found in the inspected paths.
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 unpkgThe AGENTS.md note is written during the explicit `vatio init` command; the skills hint checks installed versions and caches its display state.
lib/skills-hint.mjsView on unpkg · L32Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.103.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.103.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.