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

@voidbase-cloud/plugin-hardening

v1.0.0

Published

The hardening plugin of voidbase: provides hardening@1, the body limit, the rate limit, the response policy and GET /api/csrf

Readme

@voidbase-cloud/plugin-hardening

The hardening plugin of voidbase, as a package of its own. It provides hardening@1: PocketBase's body limit and its rate limit rules, and the response policy — the headers on every response, the files' Content-Security-Policy, CORS and the CSRF check — plus GET /api/csrf, the double-submit token.

It ships with voidbase and is on by default — @voidbase-cloud/voidbase depends on this package and loads it — so an instance needs nothing here. Install it yourself only to load it into an app that builds its own plugin graph.

The shape

  • It provides middleware rather than mounting it. Hono composes handlers in the order they were registered and the kernel loads after the routes are mounted, so a use("*") from a plugin would sit behind every route and never run. The three handlers are provided as hardening@1; the core holds their place in the chain with slots that ask the provider per request. Turn this plugin off and the limits and the policy go with it, CORS included; provide hardening@1 from another plugin and yours runs instead.
  • The one route is a route because it hands something back. GET /api/csrf is mounted whatever the knob says and answers 404 while it is off: the knob is read per request, the routes are fixed when the app is built.
  • It imports the core by name and only by name: @voidbase-cloud/voidbase/hardening-middleware (the five calls this plugin makes, published for it in 7.2 — not the three core modules behind them), /interfaces, /kernel and /plugins.
  • @voidbase-cloud/voidbase/plugins/hardening stays published forever, as a re-export of this package.

The rest of the shape — the lockstep version, the peer edge back on the core, hono declared at the core's own range, npm as the only registry this name is published to — is the template packages/plugin-realtime/README.md describes, and packages/voidbase/test/unit/plugin-extraction.test.ts asserts it over every @voidbase-cloud/plugin-* package in the workspace rather than over any one of them.

Licence

MIT, with voidbase.