@vatio-ai/cli@0.77.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 24d ago · by lpm-firewall-aiSource inspection found an explicit-command write to project agent instructions, which merits a capability warning under the agent configuration policy. The inspected code did not establish install-time execution or a concrete attack.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and declares no install lifecycle hook.
- Running the explicit init command writes a Vatio guidance note to the project AGENTS.md file.
- The skills hint checks installed skill locations and records hint state; it does not install or update agent extensions.
- Session sharing requires --yes or interactive confirmation before sending the transcript.
- The agent configuration write is tied to an explicit workspace setup command and contains package-specific guidance.
- No install-time attack, credential theft, or unrelated agent-control mutation was identified.
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 locations and records hint state; it does not install or update agent extensions.
lib/skills-hint.mjsView on unpkg · L77Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.77.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.77.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.