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

@ikenga/registry-client

v0.2.0

Published

Read-side client for the Ikenga registry. Fetches the signed index and per-pkg detail files, verifies minisign signatures, and resolves dep install plans. Used by the shell and the ikenga CLI.

Downloads

81

Readme

@ikenga/registry-client

Read-side client for the Ikenga registry. Used by the Ikenga shell and the ikenga CLI to:

  1. Fetch the signed root index (index.json) and verify its minisign signature against an embedded public key.
  2. Lazily fetch per-pkg detail files (pkgs/<short>.json).
  3. Resolve install plans — depth-first walk of @ikenga/pkg-* deps, producing an ordered list of { tarball, integrity, manifest } steps that the platform-specific installer (Rust in the shell, Bun in the CLI) consumes one at a time.

The client never touches disk. The actual download / integrity-verify / untar step is the platform installer's job; this lib just produces the plan.

Usage

import { fetchIndex, fetchPkgDetail, resolveInstallPlan } from '@ikenga/registry-client';

const REGISTRY_URL = 'https://royalti-io.github.io/ikenga-registry/index.json';
const REGISTRY_PUBKEY = 'RWRTqugAYXnZRgZPMyuqRNB3G41wg+AhSU2yT8nmDNNQlWQPeCfRXAvI';

const { index, indexUrl } = await fetchIndex({
  indexUrl: REGISTRY_URL,
  publicKey: REGISTRY_PUBKEY,
});

const detail = await fetchPkgDetail({
  indexUrl,
  entry: index.pkgs.find((p) => p.name === '@ikenga/pkg-engine-noop')!,
});

const plan = await resolveInstallPlan({
  root: detail,
  fetchDetail: (name) => fetchPkgDetail({ indexUrl, entry: { name } }),
});

for (const step of plan) {
  // hand `step` to your platform installer:
  //   shell: invoke('pkg_install_from_registry', step)
  //   cli:   await downloadAndUntarAndRegister(step)
}

Signature trust model

  • Only index.json is individually signed. Detail files are trusted by reference: the signed index names exactly which pkgs exist + what their latest version is, so a substituted detail file would either fail Zod validation or list a version the index doesn't bless.
  • The tarball URL inside a detail file is trusted because it came through the verified index. Once downloaded, the installer must re-verify the tarball's SHA-512 against PkgVersion.integrity before unpacking.
  • We sign with minisign -H (prehashed mode: Ed25519 over BLAKE2b-512(content)).

License

Apache-2.0.