@vatio-ai/cli@0.91.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook. The agent configuration finding resolves to an explicit CLI setup action, while the skills hint reads installed metadata and stores its own display state; transcript sharing is separately invoked and confirmation-gated.
Decision evidence
public snapshot- The manifest has no install lifecycle script and exposes a CLI entrypoint.
- The agent note is written during the explicit init command into the initialized workspace's AGENTS.md.
- The skills hint checks installed skill metadata and stores display-check state; its shown destination is package config state, not an agent control file.
- Session transcript sharing is a separate CLI command with a confirmation step, and sends to the configured Vatio service using the saved token.
- The improve command fetches workspace documentation using the configured service URL and token.
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 skills hint checks installed skill metadata and stores display-check state; its shown destination is package config state, not an agent control file.
lib/skills-hint.mjsView on unpkg · L77Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.91.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.91.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.