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 🙏

© 2025 – Pkg Stats / Ryan Hefner

swagger-route-validator

v3.1.0

Published

The fastest openapi validation middleware

Readme


  • The fastest request/response validator for OpenAPI applications
  • Zero dependencies :star:
  • Battle-tested by Fortune 500 companies
  • Supports OpenAPI 3.X features like $ref, $not, $anyOf, $allOf, $oneOf, etc.
  • Supports most common data formats like emails, ips, uuids, dates, etc.
  • Supports Express 4.x and 5.x
  • Uses OpenAPI/ Swagger specs as Objects. Say goodbye to YAML files!

Usage

Request validation

SRV offers a built-in express middleware for easy integration:

import {expressRequestValidation} from 'swagger-route-validator';
import express from 'express';

const app = express();

app.get('/foo', expressRequestValidation(/* An object of the route's spec */, /* The full spec */), (req, res, next) => {
  res.send('Hello World!');
});

You may also run validations directly:

import {validateRequest} from 'swagger-route-validator';

const errors = validateRequest(/* An object of the route's spec */, req, /* The full spec */);
if (errors.length > 0) throw new Error(`Request object does not match the specification for this route: ${JSON.stringify(errors)}`);

Finally, if you want to put the validation middleware earlier in the stack (before routing) you could follow this example. The middleware will try to match the request to a route from the spec. This could be used to retrospec an old API, but it is not recommenced for new services.

Response validation

SRV also offers a middleware for response validation:

import {expressResponseValidation} from 'swagger-route-validator';
import express from 'express';

const app = express();

app.get('/foo', expressResponseValidation(/* An object of the route's spec */, { behavior: 'error' }, /* The full spec */), (req, res, next) => {
  res.send('Hello World!');
});

As well as a direct validation function:

import {validateResponse} from 'swagger-route-validator';

const errors = validateResponse(/* An object of the route's spec */, body, res, /* The full spec */);
if (errors.length > 0) throw new Error(`Response object does not match the specification for this route: ${JSON.stringify(errors)}`);

Running tests

npm run test

Running benchmarks

npm run bench

Migration from 2.X to 3.X

SRV no longer has a default export, your import statement will need to change from:

import validate from 'swagger-route-validator';

To:

import {validateRequest} from 'swagger-route-validator';

SRV will now also throw errors when meet with a malformed spec Object.

License

Apache 2.0 - Frederic Charette