Sign In

@vantio/cli

Package Overview
Dependencies
Maintainers
1
Versions
19
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@vantio/cli - npm Package Compare versions

Comparing version
0.3.8
 to
0.3.9
+1
-1
package.json
{
"name": "@vantio/cli",
"version": "0.3.8",
"version": "0.3.9",
"description": "Vantio Optics CLI — wrap any AI agent and observe LLM egress. Blind by design, not a proxy. Sight Loop: wrap → capture → inspect.",

@@ -5,0 +5,0 @@ "license": "MIT",

+4
-4
README.md

@@ -5,3 +5,3 @@ # @vantio/cli

> Wrap any AI agent with **Vantio Optics** — free visibility into what it sends. Zero code changes. Current npm release: **0.3.8**.
> Wrap any AI agent with **Vantio Optics** — free visibility into what it sends. Zero code changes. Current npm release: **0.3.9**.

@@ -50,3 +50,3 @@ ```bash

Wrap any Node process with `vantio run`. The CLI intercepts outbound calls to known LLM APIs via Node `fetch`, `undici.fetch`, `undici.request` (including `Client` / `Pool` / `Agent` `.request()`), `undici.stream` / `pipeline` / `dispatch` / `connect` / `upgrade`, Node `http`/`https`, and Node `http2.connect` / `session.request`, and records connection metadata locally (and to Gate when a key is configured). For Python, install `vantio-agent-sdk` and run `vantio run python agent.py` — same wrap, no script edit. `shield()` is optional when you want a trace id inside the process.
Wrap any Node process with `vantio run`. The CLI intercepts outbound calls to known LLM APIs via Node `fetch`, `undici.fetch`, `undici.request` (including `Client` / `Pool` / `Agent` `.request()`), `undici.stream` / `pipeline` / `dispatch` / `connect` / `upgrade`, Node `http`/`https`, Node `http2.connect` / `session.request`, and Node `net`/`tls` connect to in-scope hosts, and records connection metadata locally (and to Gate when a key is configured). For Python, install `vantio-agent-sdk` and run `vantio run python agent.py` — same wrap, no script edit. `shield()` is optional when you want a trace id inside the process.

@@ -168,3 +168,3 @@ Your code doesn't change. Your agent runs normally. If you've run `vantio login`, the stored key is injected into the child process; an explicit `VANTIO_API_KEY` in your environment always takes precedence.

Auto-intercepts LLM calls when running **Node.js** processes (`node`, `tsx`, `ts-node`, `npx`) — Node `fetch`, `undici.fetch`, `undici.request`, `undici.stream` / `pipeline` / `dispatch` / `connect` / `upgrade`, Node `http`/`https`, and Node `http2`. Current npm release: **`@vantio/cli` 0.3.8**.
Auto-intercepts LLM calls when running **Node.js** processes (`node`, `tsx`, `ts-node`, `npx`) — Node `fetch`, `undici.fetch`, `undici.request`, `undici.stream` / `pipeline` / `dispatch` / `connect` / `upgrade`, Node `http`/`https`, Node `http2`, and Node `net`/`tls`. Current npm release: **`@vantio/cli` 0.3.9**.

@@ -179,3 +179,3 @@ Python, Ruby, and other runtimes are spawned normally without this interceptor — use the [Python SDK](https://pypi.org/project/vantio-agent-sdk) (`vantio-agent-sdk` **3.0.4**, `shield()`) for Python urllib / requests / httpx / aiohttp.

curl, raw sockets, and browser paths stay outside this wrap. After `undici.upgrade`, WebSocket frames on the raw socket are also outside this wrap. Phantom Engine is the Linux-host product when you need protection beneath the app wrap.
curl and browser paths stay outside this wrap. After `undici.upgrade`, WebSocket frames on the raw socket are also outside this wrap. Phantom Engine is the Linux-host product when you need protection beneath the app wrap.

@@ -182,0 +182,0 @@ ---

bin/interceptor.cjs

Sorry, the diff of this file is too big to display