@vatio-ai/cli@0.98.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe flagged skills-hint location reads plugin and project skill metadata, while its caller is a user-run CLI command and its persisted timing state is in the CLI configuration directory. No install lifecycle hook or concrete attack behavior was identified; the dependency coverage paths are YAML implementation modules.
Decision evidence
public snapshot- package.json declares the CLI entrypoint and YAML dependency, with no install lifecycle scripts.
- The AGENTS.md note is written by a CLI init helper, which adds a Vatio section only when the file does not already mention Vatio.
- The skills hint reads Claude plugin and project skill metadata; its caller invokes it during the user-run flags command, and its saved state is under the CLI config directory.
- The inspected dependency files are YAML parsing, schema, composition, logging, and stringification modules; its manifest describes a JavaScript YAML parser and stringifier.
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 reads Claude plugin and project skill metadata; its caller invokes it during the user-run flags command, and its saved state is under the CLI config directory.
lib/skills-hint.mjsView on unpkg · L77Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.98.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.98.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.