npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vane.build/sidecar

v0.1.1

Published

Zero-config sidecar proxy that attaches Vane passports to outbound calls and verifies inbound credentials

Readme

@vane.build/sidecar

A proxy process that intercepts outbound HTTP/HTTPS calls from any AI agent, attaches a valid Vane Agent Passport as a header, and records every call in the Vane attestation chain — without changing a line of agent code. Node 22+.

How it works

Run the sidecar alongside your agent and point the agent's HTTP proxy at it:

agent process → HTTP_PROXY=http://127.0.0.1:8080 → sidecar → upstream

On every outbound call the sidecar:

  1. Fetches (and caches) a Vane Agent Passport from your Vane instance
  2. Injects Vane-Passport: <cap-jwt> into the request headers
  3. Also sets Authorization: Bearer <cap-jwt> if the request has no existing Authorization header
  4. Records the call in the Vane attestation chain (fire-and-forget, never blocks)

For HTTPS, the sidecar uses transparent MITM via a locally-generated CA. The agent process must trust that CA certificate.

Installation

npm install @vane.build/sidecar
npm run build   # compiles TypeScript to dist/

Running

Set the required environment variables, then start the sidecar:

VANE_API_URL=https://api.vane.build \
VANE_API_KEY=vane_... \
VANE_AGENT_ID=my-agent \
VANE_COMPANY_ID=acme \
node dist/index.js

The sidecar prints startup instructions including the proxy address and CA certificate path:

[vane-sidecar] Proxy listening on http://127.0.0.1:8080
[vane-sidecar] Agent: my-agent  Company: acme

[vane-sidecar] ── MITM CA certificate ───────────────────────────────────
[vane-sidecar] Written to: ./vane-ca.pem
[vane-sidecar] Fetch via:  GET http://127.0.0.1:8080/vane-ca-cert.pem

[vane-sidecar] Set on your agent process:
[vane-sidecar]   HTTP_PROXY=http://127.0.0.1:8080
[vane-sidecar]   HTTPS_PROXY=http://127.0.0.1:8080
[vane-sidecar]   NODE_EXTRA_CA_CERTS=./vane-ca.pem

Then start your agent:

HTTP_PROXY=http://127.0.0.1:8080 \
HTTPS_PROXY=http://127.0.0.1:8080 \
NODE_EXTRA_CA_CERTS=./vane-ca.pem \
node my-agent.js

For Python agents use REQUESTS_CA_BUNDLE=./vane-ca.pem instead of NODE_EXTRA_CA_CERTS.

Headers injected

| Header | Value | When | |---|---|---| | Vane-Passport | <cap-jwt> | Every proxied outbound request | | Authorization | Bearer <cap-jwt> | Only when no Authorization header is already present |

Inbound verification (optional)

If SIDECAR_AGENT_TARGET is set, the sidecar also operates as a reverse proxy. Incoming requests to http://127.0.0.1:<port>/... are verified against the Vane CA public key before being forwarded to the target:

SIDECAR_AGENT_TARGET=http://localhost:3001 \
node dist/index.js

A request with a missing or invalid Vane-Passport header (or Authorization: Bearer <cap-jwt>) is rejected with 401. Verified requests are forwarded as-is.

Environment variables

| Variable | Default | Required | |---|---|---| | VANE_API_URL | — | yes | | VANE_API_KEY | — | yes | | VANE_AGENT_ID | — | yes | | VANE_COMPANY_ID | — | yes | | SIDECAR_PORT | 8080 | no | | SIDECAR_AGENT_TARGET | — | no (inbound reverse proxy only) | | SIDECAR_CA_CERT_FILE | ./vane-ca.pem | no |

CA certificate

The MITM root CA is ephemeral — generated fresh on each startup. You can fetch it at any time from:

GET http://127.0.0.1:<SIDECAR_PORT>/vane-ca-cert.pem

No authentication required. The path is also written to disk at SIDECAR_CA_CERT_FILE on startup.


Vane main repo · docs.vane.build/sidecar