@vatio-ai/cli@0.92.1
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts. Source inspection shows the flagged agent-file write is part of explicit `vatio init`, while the skills hint only reads installed-skill metadata and records local display state; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json declares the CLI entrypoint and dependencies but no lifecycle scripts.
- The project AGENTS.md note is written only by the explicit `vatio init` command.
- The skills hint checks installed Vatio skills and writes its display interval to a cache; it does not modify agent settings.
- The improve command writes a report file only when invoked with `--save`.
- The hint is skipped in CI or when VATIO_NO_SKILLS_HINT is set.
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.92.1.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.92.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.