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

@tillstack/shield-node

v0.3.0

Published

TillShield inline WAF for Node.js — Express/Connect/Fastify middleware and a raw http handler that block, challenge or rate-limit requests at your origin.

Readme

@tillstack/shield-node

TillShield inline WAF for Node.js. Block, challenge and rate-limit requests at your origin using rules you manage in the TillDev dashboard — plus the cross-customer threat-intel deny list.

Rules and the deny list are fetched from TillDev and evaluated locally on every request (no network call on the hot path). Decisions are reported back asynchronously so blocks show up in your TillShield dashboard.

Install

npm install @tillstack/shield-node

Requires Node 18+ (Node 20+ recommended for built-in WebCrypto).

Set up

Mint a project edge key in the dashboard under Shield → Inline WAF (tse_…). It's a server-side secret — keep it in an env var, never ship it to a browser.

Express / Connect

import { createShield } from '@tillstack/shield-node'

const shield = createShield({ edgeKey: process.env.SHIELD_EDGE_KEY })

app.use(shield.express())

Fastify

const shield = createShield({ edgeKey: process.env.SHIELD_EDGE_KEY })

fastify.addHook('onRequest', shield.fastifyHook)

Raw http / anything else

const server = http.createServer(async (req, res) => {
  if (await shield.handle(req, res)) return // shield served a block/challenge
  // …your handler…
})

Options

| Option | Default | Description | | --- | --- | --- | | edgeKey | — | Required. Your tse_… project edge key. | | apiBase | https://tilldev.dev | TillDev API base. | | failMode | 'open' | 'open' serves traffic if TillDev is unreachable; 'closed' blocks it. | | trustProxy | true | Read the client IP from the leftmost X-Forwarded-For. Set false behind no proxy. | | countryHeader | — | Header carrying an ISO country code (e.g. 'cf-ipcountry') to enable country rules. | | report | true | Report decisions back to TillDev. | | onDecision | — | (result, req) => void — observe every non-allow decision. | | defaultBlockBody | "Request blocked by TillShield." | Body when a rule sets none. |

How it decides

Rules run in ascending priority; the first match wins. Each rule matches on any combination of: client IP (CIDR, IPv4/IPv6), URL path glob, HTTP method, country, User-Agent regex, and a threat_intel flag (match when sha256(ip) is in the shared deny list). A rule can also carry a rate limit (requests per window, keyed by IP or IP+path) — it fires only once the limit is exceeded.

A matching rule's mode decides the outcome: block (serves its status, default 403), challenge (serves e.g. 429 with Retry-After), or log (allows through but records the match).

Notes

  • Fail-open by design. Any internal error, or an unreachable TillDev, results in the request being allowed (unless failMode: 'closed'). TillShield can't take your site down.
  • Rate limits are per-process. The built-in limiter counts within a single Node instance. For a globally-consistent limit across many instances, front your origin with @tillstack/shield-cloudflare or the drop-in TillShield edge worker.
  • No raw IPs leave your server — decision reports carry sha256(ip) only.