@vatio-ai/cli@0.85.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest exposes a CLI without an install lifecycle hook. Source inspection shows the flagged agent configuration behavior is user-invoked or limited to local hint state, and session sharing requires explicit approval; no malicious behavior was identified.
Decision evidence
public snapshot- The manifest exposes the Vatio CLI and has no install lifecycle hook.
- The project AGENTS.md write runs through explicit `vatio init`; it leaves files mentioning Vatio unchanged.
- The skills hint runs after a user command, recommends manual installation or updates, and stores its display state under Vatio's config directory.
- Sharing a session requires `--yes` or an interactive affirmative response; the upload uses the configured Vatio API base URL.
- The entrypoint dispatches the requested command and handles ordinary trial retry and error reporting.
- The support helper invokes Git to collect commit metadata for deployment traceability.
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.85.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.85.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.