@vatio-ai/skills@2.1.0
Vatio skills and MCP for Claude Code, Cursor and Codex: build and test an AI agent for the app you're building with /vatio-init, improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze. Vatio holds the agent; no config files
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package's only executable entry is a user-run installer that writes its own skills and the advertised MCP integration into the project. It sends disclosed install telemetry to Vatio with an opt-out, and the inspected source shows no harmful data collection or unrelated behavior.
Decision evidence
public snapshot- The manifest exposes bin/install.mjs as a command; it has no lifecycle script, so its setup runs when a user invokes the CLI.
- The CLI describes copying the package's skills into project agent skill directories.
- The installer adds the Vatio MCP server to project configuration, with --no-mcp to skip that step.
- Install telemetry is disclosed, can be disabled, and reports to the Vatio service; the README says it reports the skills version and coding agent.
Source & flagged code
8 flaggedRuntime or CLI source writes behavior-bearing configuration into a user or project AI-agent control surface.
bin/install.mjsView on unpkgFindings
Affected versions and remediation
This report applies to @vatio-ai/skills@2.1.0.
See all versions of @vatio-ai/skills for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/skills@2.1.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.