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

@owasp-webshield/node

v2.0.0

Published

Framework-neutral server layer for OWL (OWASP Webshield Library): per-request auth, access control, CSRF, validation, security headers, SSRF checks and error mapping on top of @owasp-webshield/core

Downloads

229

Readme

@owasp-webshield/node

Framework-neutral server layer for OWL (OWASP Webshield Library). It provides per-request authentication, access control, CSRF, validation, security headers, SSRF checks, error mapping and security logging as plain functions over @owasp-webshield/core.

Using Express? Install @owasp-webshield/express instead. It wraps these functions as middleware.

Installation

npm install @owasp-webshield/core @owasp-webshield/node

An ES module with TypeScript declarations. It needs Node.js 20.19+ or 22.12+, which can also load it from CommonJS with require().

Usage

Every function takes a Node IncomingMessage (plain node:http, Express, Connect) or a Fetch API Request, and throws a SecurityError on failure. toErrorResponse() turns any error into a safe response.

import http from "node:http";
import { assertPermission, authenticate, securityHeaders, toErrorResponse, verifyCsrf } from "@owasp-webshield/node";

const headers = securityHeaders();

http.createServer(async (req, res) => {
  try {
    const session = await authenticate(req, { verifyToken: (token) => sessionStore.lookup(token) });
    await verifyCsrf(req, { getExpectedToken: () => sessionStore.csrfTokenFor(session.userId) });
    assertPermission({ session, action: "read", resource: "reports" }, owl);
    res.writeHead(200, { ...headers, "Content-Type": "application/json" });
    res.end(JSON.stringify({ ok: true }));
  } catch (error) {
    const { status, headers: errorHeaders, body } = toErrorResponse(error);
    res.writeHead(status, { ...headers, ...errorHeaders, "Content-Type": "application/json" });
    res.end(JSON.stringify(body));
  }
}).listen(3000);

The core AuthManager/TokenManager/CSRFTokenManager each hold a single session, which suits a browser tab. These functions hold no state: verifyToken and getExpectedToken look the session up per request, so concurrent users never share one.

Exports

| Category | Exports | |---|---| | A01 Access Control | checkPermission, assertPermission, toPermissionChecker | | A03 Injection Defense | assertValidInput, sanitizeFields | | A05 Security Misconfiguration | securityHeaders, DEFAULT_SECURITY_HEADERS, assertHardened | | A07 Auth Session | authenticate, extractBearerToken | | A08 Data Integrity | verifyCsrf, issueCsrfToken, generateCsrfToken, isSafeMethod, DEFAULT_CSRF_COOKIE, DEFAULT_CSRF_HEADER | | A09 Logging Monitoring | logRequestError, requestLogContext | | A10 SSRF Defense | assertSafeOutboundUrl | | Errors | toErrorResponse, statusForSecurityError | | HTTP helpers | getHeader, getMethod, getPath, getCookieValues, serializeCookie |

A02 (crypto), A04 (design guard) and A06 (dependency scanning) have no per-request step. Use them from @owasp-webshield/core directly.

Documentation

License

Apache-2.0. See the main repository for the full license text and contribution guidelines.