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

@nexpress/plugin-oauth-github

v0.4.6

Published

GitHub OAuth provider plugin for NexPress.

Readme

@nexpress/plugin-oauth-github

"Sign in with GitHub" plugin for NexPress. Wires GitHub as an OAuth provider for both staff and member auth pools.

Install

pnpm add @nexpress/plugin-oauth-github
// nexpress.config.ts
import githubOAuth from "@nexpress/plugin-oauth-github";

export default defineConfig({
  // ...
  plugins: [githubOAuth],
});

Configuration

Two paths — pick whichever fits the operator's secret-management story. The plugin is safe to leave installed with no credentials; in that case it logs an informational setup hint and registers no provider.

1. Environment variables (recommended for production)

NP_OAUTH_GITHUB_CLIENT_ID=Iv1.xxxxxxxxxxxx
NP_OAUTH_GITHUB_CLIENT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxx

Works with Doppler / 1Password CLI / AWS Secrets Manager / Kubernetes secrets — anything that injects env at boot. Secrets never touch the database.

2. Admin auto-form

Open /admin/plugins/oauth-github after the framework boots. The G.1 auto-form renders these editable fields:

| Field | Type | Default | | ------------- | ----------------- | --------------------------- | | Client ID | text | empty | | Client secret | password (masked) | empty | | Scopes | one item per line | read:useruser:email | | Audience | select | staff |

Saved values persist to the current site's np_settings (key="plugin.config:oauth-github") row.

Precedence

Env wins on a tie. When NP_OAUTH_GITHUB_CLIENT_ID / NP_OAUTH_GITHUB_CLIENT_SECRET are non-empty, the admin-form values are ignored — env-driven deploys upgrade safely without surprise. Set the env vars to empty (or unset them) to switch to admin-form control. The Audience field still comes from plugin config and defaults to staff.

Set both env vars or neither. A partial env source is treated as a misconfiguration and the provider is not registered; run pnpm run doctor -- --fix-plan to surface the same problem before boot.

Request-time site isolation

The provider resolves activation, credentials, scopes, and Audience inside the current site scope for each OAuth request. Admin-form changes take effect without reload, and concurrent sites can use different OAuth apps or audiences without sharing secrets.

OAuth app callback URL

Register exactly the callback URL for the configured Audience:

  • staff: ${SITE_URL}/api/auth/oauth/github/callback
  • member: ${SITE_URL}/api/members/oauth/github/callback

GitHub OAuth Apps accept one Authorization callback URL. The bundled plugin therefore exposes one github provider to one login surface at a time, defaulting to staff. Switch Audience to member only when the GitHub OAuth App is registered for the member callback.

License

MIT