@vatio-ai/skills@1.27.0
Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe vatio-init skill explicitly instructs an agent to send a named environment or .env secret to Vatio without asking the user. This is credential exfiltration without consent, even though the transfer is tied to configuring a Vatio agent.
Decision evidence
public snapshot- The vatio-init skill is triggered when a user asks to create or set up a Vatio agent.
- The skill directs the agent to read a KEY value from the shell environment or project .env file and send it to Vatio without asking the user.
- The README identifies vatio.ai as the service the CLI talks to.
- The package installer has no lifecycle scripts; it copies the package's skills when the user runs its CLI.
- The skill limits the operation to a named secret and says not to print or copy the value into a file.
Source & flagged code
5 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@1.27.0.
See all versions of @vatio-ai/skills for other recorded verdicts.
- Avoid installing @vatio-ai/skills@1.27.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.