@vatio-ai/cli@0.90.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete attack behavior. The relevant agent configuration change is part of the CLI setup flow, and transcript sharing requires confirmation or an explicit `--yes` option before sending to the configured service endpoint.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint, lists only yaml as a dependency, and contains no lifecycle script.
- The `init` flow writes a Vatio note into the workspace AGENTS.md.
- Skills discovery reads existing agent plugin metadata and local skill directories.
- Session sharing is selected through the CLI command and requires confirmation or `--yes` before upload.
- The transcript upload uses the configured Vatio base URL and token; the base URL resolves from environment, saved config, or the package default.
- Codex session scrubbing redacts strings and omits image content.
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 unpkgSkills discovery reads existing agent plugin metadata and local skill directories.
lib/skills-hint.mjsView on unpkg · L77Findings
Affected versions and remediation
This report applies to @vatio-ai/cli@0.90.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.90.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.