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

@passport-next/passport

v4.0.0

Published

Simple, unobtrusive authentication for Node.js.

Readme

Passport-Next/Passport

Status: NPM version Build Status Coverage Status Maintainability Dependencies SAST

About

Passport-Next/Passport is a Connect and Express-compatible authentication middleware for Node.js.

Passport's sole purpose is to authenticate requests, which it does through an extensible set of plugins known as strategies. Passport does not mount routes or assume any particular database schema, which maximizes flexibility and allows application-level decisions to be made by the developer. The API is simple: you provide Passport a request to authenticate, and Passport provides hooks for controlling what occurs when authentication succeeds or fails.

Install

$ npm install @passport-next/passport

Migrating from 3.x

Most authentication strategies that worked with Passport 3.x should continue to work with 4.x without modification. Passport still accepts strategy instances that implement authenticate(request, options) and augments them with the standard success, fail, redirect, pass, and error actions. Strategies do not need to extend the current Strategy class or pass an instanceof check.

Applications must run a supported Node.js version and load Passport as native ESM. The default export is the Passport singleton; constructors and strategy base classes are named exports:

import passport, { Passport } from '@passport-next/passport';

const customPassport = new Passport();
app.use(passport.initialize());
otherApp.use(customPassport.initialize());

Custom strategies that import Passport's strategy base class should update their imports for ESM. Application-level serializers, deserializers, and auth-info transforms also require the 4.x request-first signature and may use a callback, synchronous return value, or Promise. These migration requirements apply to application hooks around a strategy, not to the strategy's usual authenticate() implementation. See CHANGELOG.md for the full list of breaking changes.

Docs

Please see the wiki

Need help?

Please raise an issue and/or ask a question on Stackoverflow with the passport.js tag.

Support policy

We support all node versions supported by the Node Foundation

Contributing

Please see CONTRIBUTING.md