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

wkr-auth-mock

v1.1.1

Published

Kinda mocks the wkr auth service, but mostly just allows for generating JWTs and verifying them against a JWKS endpoint.

Downloads

3

Readme

wkr-auth-mock

Kinda mocks the wkr auth service, but mostly just allows for generating JWTs and verifying them against a JWKS endpoint.

NOTICE: This should not be used in production, or anywhere that is publicly accessible. It uses hard-coded keys, committed in the repo. Counterfeit JWTs can easily be created by simply looking at the source code of this application. The intended purpose of this application is testing.

Development

Run the linter:

npm run watch

Integration Tests

NOTE: These tests probably only work on macos, since using gtimeout and greadlink in the wait-for-it.sh script.

NOTE: If running on macos, you will need coreutils installed.

brew install coreutils

Run integration tests:

npm run test:integration

Usage

This command starts up a service running on a specified port. The command is added to npm's bin as wkr-auth-mock.

Usage: wkr-auth-mock -p <num> -c <string>

Options:
  --version  Show version number                                       [boolean]
  -h         Show help                                                 [boolean]
  -p         The port to listen on.                                   [required]
  -c         The claims namespace store custom parameters (e.g. permissions) in
             the JWT.                                                 [required]

The service exposes several endpoints.

The issuer and audience for JWTs will be set to: wkr-auth-mock

/jwt

Get a JWT. All provided parameters will be set in the JWT under the claims namespace provided when running the command.

Method: POST

Content Type: application/json

Parameters:

  • lasts (int, default: 3600) How long the JWT should last, in seconds.
  • account (object, optional, default: {}) The account info to set in the JWT.
  • permissions (array, optional, default: []) The permissions to set in the JWT.
  • roles (array, optional, default: []) The roles to set in the JWT.
  • groups (array, optional, default: []) The groups to set in the JWT.

Result:

Status: 200, 500 (on error)

  • token (object, optional) The JWT. May not be set if there was an error.

/jwks.json

The JWKS endpoint.

Method: GET