@vatio-ai/cli@0.83.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged configuration writes are tied to explicit CLI commands with limited scope. The transcript upload is gated by confirmation and sends the Vatio token to the configured Vatio API base URL.
Decision evidence
public snapshot- package.json exposes the CLI entrypoint and has no lifecycle hook; its runtime dependency is yaml.
- The AGENTS.md update runs in the explicit init command, writes a short workspace note, and leaves files already mentioning Vatio unchanged.
- The skills hint reads agent installation metadata and caches its reminder under Vatio config; it is called by improve commands and can be disabled.
- Transcript sharing asks for confirmation and sends only after consent; the bearer token goes to the configured Vatio API base URL.
- The CLI dispatches share-session as a named command; its trial recovery path only retries the command after a claimed-trial response.
- The inspected 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.83.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.83.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.