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

@8lines/gauntlet-next-adapter

v0.1.8

Published

Next.js App Router bridge for exposing an explicitly registered Gauntlet adapter catalog through normalized Web Requests.

Readme

Gauntlet Next.js bridge

This thin App Router bridge accepts only a normalized Web Request. It does not see the original raw target and never claims native raw-target equivalence. It contains no dashboard UI. A trusted ingress is mandatory: it alone receives untrusted traffic, rejects percent escapes, dot segments, repeated slashes, backslashes, query/fragment syntax, and literal SP/HTAB before forwarding, strips every client-supplied X-TC-* and X-Forwarded-* header, and returns a fixed malformed 400 even when the upstream adapter is disabled.

// app/%5Fgauntlet/v1/[...gauntlet]/route.ts
import { createGauntletRouteHandler } from "@8lines/gauntlet-next-adapter";
import { catalog } from "../../../../gauntlet/catalog.js";

const handler = createGauntletRouteHandler({
  enabled: process.env.GAUNTLET_ENABLED === "true",
  catalog,
});

export const runtime = "nodejs";
export const dynamic = "force-dynamic";
export const revalidate = 0;
export const GET = handler;
export const POST = handler;
export const PUT = handler;
export const PATCH = handler;
export const DELETE = handler;
export const OPTIONS = handler;
export const HEAD = handler;

The relative import above points to the application's gauntlet/catalog.ts. Build that module with the compile-checked Core example. The repository's runnable Next fixture shows the same composition in its route module.

Use runtime = "nodejs", dynamic = "force-dynamic", and revalidate = 0. Next treats a leading _ directory as private, so the literal URL segment _gauntlet must use its documented filesystem escape %5Fgauntlet; never replace it with a dynamic first segment. skipTrailingSlashRedirect and skipProxyUrlNormalize are useful hardening, not raw-target recovery. Use native Node when the package must own the complete raw-target and disabled-precedence contract. Deny /_gauntlet/* at public ingress, expose it only on private environment networking, and leave GAUNTLET_ENABLED absent outside non-production environments. The adapter publishes only registered Core operations/capabilities and is never a generic application-route proxy or arbitrary executor.

Documentation index