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

@keyring-dev/core

v0.1.1

Published

Framework-free API key verification for Keyring. Zero network calls on the hot path.

Readme

@keyring-dev/core

Framework-free API key verification. No Express, no Fastify, no HTTP types, no I/O, no promises. Every Keyring framework adapter wraps this package, and every other language SDK is held to the same conformance fixtures it is.

MIT licensed.

import { mintKey, MemoryPolicyStore, verify } from '@keyring-dev/core';

const minted = mintKey({ env: 'live' });
// Persist minted.lookupHash and minted.displayPrefix.
// Show minted.plaintext.expose() once, then forget it.

const result = verify(presentedKey, {
  store, // your local policy cache
  env: 'live', // the environment this call site serves
  requiredScopes: ['read:orders'],
});

if (!result.ok) {
  // result.code / result.status / result.message are safe to return.
  // result.reason is for your log only: every 401 looks identical to the
  // caller, deliberately.
  return respond(result.status, {
    error: result.code,
    message: result.message,
  });
}

result.key.tenantId; // who is calling
result.key.env; // 'live' | 'test' -- branch your data access on this

What it will not do

  • Make a network call. PolicyStore.get is synchronous so that a remote lookup on the verification path is not expressible.
  • Tell an unauthenticated caller why a key failed. Not-found, revoked and expired are one response; the distinction goes to your request log.
  • Hold a pepper. The peppered hash is a control-plane value and lives in a package that is never published.
  • Give you a key back. The plaintext exists once and is not recoverable.

Key format

kr_live_ / kr_test_, 24 random bytes as base64url, and a CRC-32 checksum over the prefix and body. The environment is inside the hashed material, so a test key can never resolve to env: 'live'.