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/identity

v0.4.2

Published

Volter identity for products: whether an issuer is available, who a token names (ADR-0001), and this machine's one shared sign-in (`volter login`).

Readme

@volter/identity

What a product needs from Volter's identity service (https://id.volter.ai), and nothing it can do without.

import { resolveIdentity, verifyIdentityToken } from "@volter/identity";

// Whether this deployment has an identity service at all (a CDN-only self-host has none).
const identity = await resolveIdentity(process.env.VOLTER_ISSUER);

// Who a token names, verified against the issuer's published keys, with no call per request.
const person = await verifyIdentityToken(token, { issuer: "https://id.volter.ai", audience: "https://your-product.example" });
person.subject;   // the permanent Volter id
person.email;     // when the email scope was granted
person.githubId;  // the linked GitHub account's numeric id, when one is linked

subject is permanent; everything else may change. githubLogin is the login recorded when the person first signed in with GitHub: a GitHub login can be renamed and re-registered, and an identity that linked GitHub later carries only githubId. Key a GitHub account by githubId, and read its current login from GitHub (GET /user/{id}) wherever the login decides access. Tokens are EdDSA JWTs; access tokens for a registered resource carry it as their audience.

This machine's one sign-in

signIn signs the machine in once, for every Volter tool (volter login runs it); a tool then asks tokenFor(itsOrigin) for a token of its own. In the browser, the sign-in returns to a page served by the machine itself, which stays open until the tool is done: finish may ask the person one question there and says what the page ends on.

await signIn({
  prompt: ({ url, opened }) => console.error(opened ? `Finish in your browser: ${url}` : `Open ${url}`),
  finish: async ({ who, ask }) => {
    // `ask` is absent when there is no tab to ask in (a device code): ask at the terminal instead.
    const chosen = ask ? await ask({ title: "Choose your teams", options: [{ id: "t1", label: "Volter", checked: true }], submit: "Continue" }) : ["t1"];
    return { ok: true, title: "You're signed in", items: chosen.map((id) => ({ label: id })) };
  },
});