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

@qorechain/handles

v0.1.0

Published

Resolve a QoreX @handle to an address — signature-verified against a pinned registry key, with trust-on-first-use pinning left to the caller.

Readme

@qorechain/handles

Resolve a QoreX @handle to an address.

This is not a lookup client. Every resolution is verified against a pinned ed25519 registry public key — an answer the registry could forge is never returned — and then checked against a trust-on-first-use pin.

The pin store is injected rather than built in, and that is the point: a pin exists to detect that the registry started saying something different, so it must be held by someone other than the party being checked. Store it on the user's device, not on the same infrastructure that serves the answer.

import { HandleClient } from "@qorechain/handles";

const client = new HandleClient({ baseUrl, registryPubkeyHex });
const { record, pin } = await client.resolve("@alice", pins);

if (pin.status === "CHANGED") {
  // Stop. Show both addresses in full and require explicit confirmation.
  // Never silently update the pin.
}

resolve does not auto-pin. Pin after the user has seen the address and proceeded — pinning earlier records an address nobody looked at.

reverse(address) returns a handle for display only. A reverse result must never become the destination of a send.