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

@forwardimpact/svcoidc

v0.1.6

Published

GitHub Actions OIDC exchange front — validates a workflow OIDC token and mints a repo-scoped installation token without holding signing material.

Readme

Oidc

GitHub Actions OIDC exchange front — validates a workflow OIDC token and mints a repo-scoped installation token without holding signing material.

What this service owns

services/oidc is the public-facing front of the hosted control plane's credential path. A GitHub Actions workflow presents its OIDC token; the service verifies that identity and returns a repo-scoped installation token minted by services/ghserver. It holds no signing material — it mirrors the services/oauthservices/ghuser protocol-front pattern, where the only publicly-listening process never touches the App private key.

Token exchange contract

POST /token
Authorization: bearer <github-actions-oidc-token>
→ 200 { installation_token, expires_at }

The workflow requests its OIDC token with the configured audience (fit-ghserver). services/oidc:

  1. verifies the JWS signature against the issuer's JWKS, plus iss, aud, exp, and nbf;
  2. extracts the repository claim as {owner}/{name};
  3. calls services/ghserver.MintInstallationToken({ owner, name }) over the control-plane internal network;
  4. returns the resulting installation token.

Failure mapping

| Condition | HTTP | | ------------------------------- | ---- | | Missing Authorization: bearer | 401 | | Invalid signature / expired | 401 | | Wrong issuer / wrong audience | 403 | | Missing repository claim | 400 | | Repo not provisioned (mint) | 404 | | Per-tenant rate limit (mint) | 429 |

JWKS rotation

GitHub's OIDC issuer or JWKS endpoint may rotate. The JWKS is cached for a bounded TTL (jwks_ttl_ms, default 10 minutes); on a signature-verification failure the validator invalidates the cache once and retries, recovering from rotation without a forced restart.

Configuration

Loaded via createServiceConfig("oidc"):

| Env var | Default | Purpose | | -------------------------- | ------------------------------------------------ | ---------------------------------------- | | SERVICE_OIDC_PROVIDER | ghserver | Mint backend (resolved as a gRPC client) | | SERVICE_OIDC_ISSUER | https://token.actions.githubusercontent.com | Expected OIDC iss | | SERVICE_OIDC_AUDIENCE | fit-ghserver | Expected OIDC aud | | SERVICE_OIDC_JWKS_TTL_MS | 600000 | JWKS cache TTL (ms) | | SERVICE_OIDC_PORT | 3008 | Listen port |

Running

Add oidc to config/config.json under init.services (see config/CLAUDE.md for entry format). In single-tenant deployments the service is not started — the bridge reads KATA_APP_PRIVATE_KEY directly. services/oidc is exposed through the same tunnel-fronted ingress pattern that services/oauth already uses.