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

@volter/conduit

v0.1.1

Published

Authenticated discovery and protocol bindings for environment services

Readme

Conduit

Authenticated discovery and authorized protocol bindings for environment services. Phase 1, published as @volter/conduit 0.1. It has no UI, engine or mandatory daemon.

@volter/conduit/protocol, /client and /server are dependency-free ES modules using Fetch APIs. Importing them starts nothing. The host embeds createHost() and supplies authentication and service adapters. createClient() connects to that host through a trusted credential-bearing fetch function.

The environment contract defines identity, discovery and scope. The implemented HTTP profile supports discovery, finite HTTP requests and release. The optional Node WebSocket proxy adds guarded ongoing connections; actual PTY product adapters remain outstanding. It does not yet implement automatic invalidation subscriptions, native file services, or provider deployment. Do not advertise a scoped service until its adapter enforces that scope.

import { createHost } from '@volter/conduit/server';
import { createNodeHandler } from '@volter/conduit/node';
import { createClient } from '@volter/conduit/client';

// the host: one service, its adapter enforcing the scope it grants
const host = createHost({
  identity: { authorityId: 'my-host', environmentId: 'env-1', generation: String(Date.now()) },
  label: 'My environment',
  authenticate: async (request) => request.headers.get('authorization') === `Bearer ${token}` ? 'owner' : null,
  services: [myService], // { id, describe(principal), authorize(principal, scope), handle({ request, path, grant }) }
});
http.createServer(createNodeHandler({ handle: host.handle, origin: 'https://env.example' })).listen(8080);

// a client: discover, bind by the protocol it needs, use the binding
const client = createClient({ baseUrl: 'https://env.example', trustedFetch: (url, init) => fetch(url, { ...init, headers: { authorization: `Bearer ${token}` } }) });
const descriptor = await client.refresh();
const binding = await client.bind('container', { protocol: descriptor.services[0].protocol });
const answer = await binding.request('/_ping');

A binding lives for the host's bindingTtlMs (five minutes by default) and is not renewed: a channel on it ends when it expires, and the client binds again. /node-websocket needs ws (an optional peer dependency); the other entries need nothing. The WebSocket proxy checks no Origin itself: an embedding that authenticates upgrades by cookie must check Origin in its authenticate.

The broader design and ordered delivery are in the integration specification. The implementation queue is ROADMAP.md. Contract verification uses real HTTP servers and filesystem bytes; run npm test inside an owned World. Install locked development dependencies with npm ci; npm run check:types checks a consumer against the public declarations. TypeScript is development-only.

Node hosts may pass createNodeHandler({handle: host.handle, origin}) from @volter/conduit/node to Node's createServer. The embedding configures the trusted external origin and owns listening, TLS/proxy policy and lifecycle. The HTTP adapter uses Node built-ins; the separate /node-websocket entry uses the installed ws dependency. TypeScript consumers of the Node entries need Node types. Browser consumers keep using the Fetch-native entries.