@vatio-ai/cli@0.82.1
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe inspected source supports a clean verdict: the package has no install hook, and agent-related file writes are scoped to explicit workspace setup or local reminder caching. Transcript sharing requires the dedicated command and affirmative confirmation by default, and sends its token to the configured API, defaulting to Vatio.
Decision evidence
public snapshot- package.json exposes the CLI entrypoint and declares no install lifecycle hook.
- The AGENTS.md write is reached through the explicit init command; it preserves files that already mention Vatio and adds workspace guidance.
- The skills hint reads agent installation state, checks the Vatio skills registry, and stores reminder state locally.
- Transcript sharing is a separate CLI command. Without --yes it prompts in a terminal and refuses to send in noninteractive use; the upload includes the configured API token.
- The upload targets the configured Vatio API, whose default base URL is https://vatio.ai.
- The flagged child process helper invokes git with fixed arguments to read repository metadata.
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.82.1.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.82.1 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.