@vatio-ai/cli@0.81.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe explicit init command writes behavior-bearing guidance into a coding-agent control file, which warrants a warning under the agent configuration policy. Its project-scoped, Vatio-specific behavior does not establish an unconsented installation-time attack.
Decision evidence
public snapshot- package.json exposes the CLI through a bin entrypoint.
- The CLI routes the explicit init command to its init handler.
- Init calls the project AGENTS.md writer.
- The AGENTS.md note points agents to Vatio documentation and workflow commands.
- The writer only targets AGENTS.md in the project and leaves a file alone if it already mentions Vatio.
- The skills hint checks installed plugin metadata and is called from an improve command.
- The AGENTS.md change requires a user to run init and is limited to a Vatio-specific project note.
- The skills hint checks installation state and records hint state; it does not install or modify agent extensions.
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.81.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.81.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.