@vatio-ai/cli@0.97.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe flagged agent configuration behavior is either read-only discovery or a project note written only by the explicit `init` command. The package manifest has no install lifecycle hook, and the inspected YAML dependency source implements parsing and serialization.
Decision evidence
public snapshot- package.json exposes a CLI binary and YAML dependency without lifecycle scripts.
- The AGENTS.md note is created or appended by the explicit `vatio init` command after it checks the target workspace; the write is not an install hook.
- The skills hint reads Claude Code plugin metadata and project skill locations to identify installed Vatio skills; it does not write agent configuration.
- The declared YAML dependency source is parser, composer, schema, and serializer code, and its manifest has no install scripts.
- The CLI dispatches explicit user commands; update checks are runtime CLI 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 unpkgFindings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.97.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.97.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.