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 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-jwt-replay-guard

v1.0.3

Published

prevents malicious people from performing replay attacks using stolen JWT tokens

Downloads

7

Readme

node-jwt-replay-guard

prevents malicious people from performing replay attacks using stolen JWT tokens.

Install

npm i node-jwt-replay-guard --save

How to use

  1. Set your JWT token secret at init using the setJWTSecret('JWT SECRET GOES HERE') method. If you don't set it, the library will try to use an environment variable called JWT_SECRET accessed through process.env.JWT_SECRET.
  2. Whenever you create a JWT token (like after a successful login call), call the storeToken(token, req) method and pass in the token and express req variables.
  3. Lastly, you can use replayGuard as a middleware on any routes that expect a JWT token to be passed through. It will check to make sure the JWT token is being used by the same IP address which last successfully logged in to the system.

Example (express)

const express = require('express');
const jwt = require('jwt-simple');
const njrg = require('node-jwt-replay-guard');
const app = express();

const JWT_SECRET = 'test';
njrg.setJWTSecret(JWT_SECRET);

app.post('/login', (req, res) => {
  // do login logic then create a jwt token and store it in the cache
  const token = jwt.encode({
    name: 'Josh Terrill',
    email: '[email protected]',
    roles: ['admin']
  }, JWT_SECRET);
  njrg.storeToken(token, req);
  res.json({token});
});

app.post('/test', njrg.replayGuard, (req, res) => {
  res.json({hello: 'world'});
});

app.listen(3000, () => {
  console.log('Server listening on port 3000.');
});

Contact

Josh Terrill [email protected]