registry / @vatio-ai/cli / 0.107.0
@vatio-ai/cli@0.107.0
Vatio CLI — deploy and manage Vatio agent workspaces
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged AGENTS.md mutation occurs only during explicit workspace initialization. Credential transfers inspected are Vatio service operations or session sharing guarded by affirmative consent; the YAML dependency evidence contains parsing and serialization code.
Static reason
No blocking static signals were detected.
Trigger
A user invokes the vatio init command.
Impact
The file receives workspace-specific guidance; no unconsented agent control change or other attack was established.
Mechanism
Initialization writes a Vatio section to the workspace AGENTS.md file, or appends the section when the existing file does not already mention Vatio.
AI rationale
The package has no install lifecycle hook, and the flagged AGENTS.md mutation occurs only during explicit workspace initialization. Credential transfers inspected are Vatio service operations or session sharing guarded by affirmative consent; the YAML dependency evidence contains parsing and serialization code.
Evidence
AGENTS.md
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entry point and declares no lifecycle hook; the bundled YAML dependency files implement parsing and serialization.
- The flagged AGENTS.md write is reached through the explicit init command and adds a Vatio workspace note, preserving existing Vatio notes.
- Authentication and API requests use the configured Vatio service URL for their stated CLI operations.
- Session sharing sends a transcript only after an affirmative terminal response or explicit --yes; telemetry is disclosed and can be disabled.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 flaggedlib/skills-hint.mjsView file
•Manifest-trigger-reachable source links an external AI-agent control path to a behavior-bearing write operation.
import { existssync, mkdirsync, readfilesync, writefilesync } from "node:fs";
import { homedir } from "node:os";
import { dirname, join, resolve } from "node:path";
import { confighome } from "./config.mjs";
import { paint } from "./support.mjs";
const skill = "vatio-improve";
const version_file = ".vatio-sk[redacted]";
const latest_url = "https://registry.npmjs.org/@vatio-ai/skills/latest";
const show_every_ms = 24 * 60 * 60 * 1000;
const check_every_ms = 24 * 60 * 60 * 1000;
const fetch_timeout_ms = 1_500;
export async function printskillshint(startdir = process.cwd()) {
if (process.env.ci || process.env.vatio_no_skills_hint) return;
const path = join(confighome(), "sk
High
Trigger Reachable External Ai Agent Control Surface Mutation
Manifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
lib/skills-hint.mjsView on unpkglib/commands/support-commands.mjs#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 5
Findings
2 High2 Medium8 Low
HighTrigger Reachable External Ai Agent Control Surface Mutationlib/skills-hint.mjs
HighSemantic Analysis Limitedlib/commands/support-commands.mjs#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencelib/commands/misc.mjs
LowAi Review Evidencelib/commands/support-commands.mjs
LowAi Review Evidencelib/commands/auth.mjs
Affected versions and remediation
This report applies to @vatio-ai/cli@0.107.0.
See all versions of @vatio-ai/cli for other recorded verdicts.
- Review the evidence and your use of @vatio-ai/cli@0.107.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.