@vatio-ai/cli@0.100.2
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack. The flagged agent configuration write is part of explicit workspace initialization, and the separate skills hint does not install or update agent extensions.
Decision evidence
public snapshot- The package manifest exposes a CLI and declares yaml as its only runtime dependency; it has no install lifecycle hook. The inspected yaml source is parser and stringifier code.
- The AGENTS.md note is written during the explicit init command and contains Vatio workspace guidance. The skills hint is guarded and records display state in the CLI config directory.
- The bounded runtime/dependency source review found no attack behavior.
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 init command and contains Vatio workspace guidance. The skills hint is guarded and records display state in the CLI config directory.
lib/skills-hint.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.100.2.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.100.2 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.