@vatio-ai/skills@2.2.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 writes are part of its documented, user-invoked setup flow and target the project configuration and skill directories. Its install telemetry is disclosed, limited to install/session and coding-agent details, and can be disabled.
Decision evidence
public snapshot- The package exposes bin/install.mjs as a user-run CLI; package.json declares no lifecycle scripts.
- The CLI documents copying its skills into the selected project and adding the Vatio MCP endpoint to project config.
- The installer copies skills shipped with this package and adds an MCP entry while preserving existing config.
- Install telemetry is disclosed in the CLI and README, and can be disabled with VATIO_TELEMETRY=0 or DO_NOT_TRACK=1.
- The install event goes to Vatio and reports the install command, package version, session ID, and detected coding agent.
Source & flagged code
7 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.2.0.
See all versions of @vatio-ai/skills for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/skills@2.2.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.