@vatio-ai/cli@0.93.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook or runtime self-dependency. Source inspection shows the agent-related write is part of explicit workspace initialization, while the skills hint checks installation state and offers guidance; no attack behavior was identified.
Decision evidence
public snapshot- package.json declares the CLI entrypoint and a yaml dependency, with no lifecycle script or runtime self-dependency.
- The `vatio init` command writes a workspace manifest and an AGENTS.md note when explicitly invoked.
- The skills hint checks for installed Vatio skills and records whether its message was shown; its version check contacts the npm registry.
- The improve commands are ordinary user-invoked CLI operations.
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.93.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.93.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.