@vatio-ai/cli@0.80.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe package has no npm lifecycle hook or runtime self-dependency, and the flagged agent-facing effects require explicit CLI use. The credential-bearing session transfer is user-invoked, approval-gated, and directed to the configured Vatio API.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and a single runtime dependency; it defines no lifecycle hook or self-dependency.
- The AGENTS.md note is written during the explicitly invoked `vatio init` command as part of local workspace setup.
- The skills hint checks existing agent skill metadata and stores a local reminder timestamp; it displays a hint rather than installing or updating an extension.
- `share-session` is an explicit CLI command. Without `--yes`, it requires terminal confirmation and refuses to send in noninteractive use.
- The confirmed session submission sends a transcript and the Vatio token to the configured Vatio API endpoint; the default service URL is vatio.ai.
- The normal success and error paths report run results through telemetry, which can be disabled; the events endpoint and token use the same configured service base URL.
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.80.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.80.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.