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

@verivyx/paywall

v0.3.2

Published

Zero-dependency x402 paywall SDK for publishers

Downloads

1,842

Readme

@verivyx/paywall

Zero-dependency x402 paywall SDK core for publishers — gate content from AI bots, charge agents on-chain via the Stellar/x402 protocol, let humans read free, and serve search crawlers an SEO preview.

Most apps should use a framework adapter (one middleware file), not the core directly: @verivyx/paywall-next · @verivyx/paywall-express · @verivyx/paywall-hono. The core is installed automatically as their dependency.

Install

npm i @verivyx/paywall

Quickstart (low-level, Fetch API)

import { verivyx } from "@verivyx/paywall";

const vx = verivyx();   // reads VERIVYX_TOKEN from env

// Wrap any Fetch-API handler — verified/paid requests pass through; bots get a 402.
export const GET = vx.protect(async (req) =>
  Response.json({ content: "..." }),
);

// Or get a decision and act on it yourself:
const decision = await vx.protect(req, { slug: "my-article" });
if (!decision.allowed) return decision.response();

Also exported: buildUnlockHtml / buildSeoPreviewResponse (preview + in-page PoW unlock pages used by the adapters), getCookie, classify, createSearchCrawlerVerifier.

Config

All options can be passed to verivyx(opts) or set via environment variables (code args win).

| Option / env var | Required | Description | |---|---|---| | VERIVYX_TOKEN | yes (server-only) | Your site token from the Verivyx dashboard — it alone identifies your site | | VERIVYX_DOMAIN | no | Optional legacy/analytics label, e.g. example.com. Not required and not part of onboarding — the token identifies your site. | | match / VERIVYX_MATCH | no | Glob patterns to gate. Empty = nothing gated. Env accepts a comma-separated list. | | failMode / VERIVYX_FAIL_MODE | no | Backend unreachable: teaser (default) | open | closed | | timeoutMs / VERIVYX_TIMEOUT_MS | no | Timeout in ms for the quick classify/requirements call (default 800). | | settleTimeoutMs / VERIVYX_SETTLE_TIMEOUT_MS | no | Timeout in ms for the authorize/settle call that awaits the on-chain payment (default 60000). Kept separate so a paying agent is never aborted mid-settle. |

This package is @verivyx/paywall 0.3.1 (token-only). The framework adapters are 0.7.0.

Docs

https://docs.verivyx.com/docs/sdk