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

@knock-dev/verify

v0.1.0

Published

A site's check of a Knock in its own server: V1–V8, with ENS on mainnet and the human's binding on World Chain

Readme

@knock-dev/verify

A site's check of a Knock, inside its own server: a press on a Wedgie, a USB device bound to one human with World ID and named in ENS. It runs the checks V1 to V8 in order and fails closed. It reads the name's records from ENS on Ethereum mainnet, the human's binding from World Chain, and the press from the Wedgie's P-256 signature under the key ENS holds. What a knock uses up is written all at once, once every check has passed.

bun add @knock-dev/verify
import { Refusal, Verifier, memoryStore } from '@knock-dev/verify'

const verifier = new Verifier({ origin: 'https://club.example', store: memoryStore() })

// POST /knock/challenge: its challenge goes to door-sdk's knock() on the page
const { challenge } = await verifier.challenge()

// POST /knock/verify, with the knock the page sent back
try {
  const knocked = await verifier.verify(assertion, { action: 'enter' })
  console.log(`in: ${knocked.name}, human ${knocked.nullifier}`)
} catch (e) {
  if (e instanceof Refusal) console.log(`refused at check ${e.check}: ${e.why} (${e.error})`)
  else throw e
}

memoryStore() keeps the challenges, each Wedgie's counter and each human's entries in the process's memory, which does for one process. libsqlStore() keeps them in SQLite or Turso, with a client from @libsql/client. It reads the chains over public RPCs unless you pass your own. It runs in your server, never in the visitor's browser.

The page's side is @knock-dev/door-sdk. For a server in another language, knock-verifier runs the same checks as a service.

Check knocks in your server shows it in use, with every setting. The reference has every export, and the checks reference each refusal.

MIT licensed.