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

@learning-with-court/cli

v0.12.0

Published

CLI for learning-with-court — proxies MCP and bootstraps workshop projects.

Readme

@learning-with-court/cli

CLI for the learning-with-court platform. Two modes:

  1. Stdio MCP proxy (default): forwards tool calls from a local agent to the hosted MCP server at mcp.workshop.institute. Auth resolves via env var (LWC_TOKEN) → cached ~/.lwc/token.json → browser sign-in.
  2. Subcommands for one-shot operations:
    • setup <workshop-id> [--dir <path>] — clone a workshop project repo (default: ~/learning-with-court/<workshop-id>/). Pass --dir to install somewhere else; the CLI auto-creates parent directories.
    • refresh <workshop-id> — refresh the clone token and git pull.
    • auth login / auth logout — manual control of the cached token.

Usage

# Bootstrap a workshop project (default: ~/learning-with-court/<workshop-id>/)
npx -y @learning-with-court/cli@latest setup mcp-workshop

# Install into a folder of your choice instead
npx -y @learning-with-court/cli@latest setup mcp-workshop --dir ~/workshops/mcp-workshop

# Run as MCP proxy (configured by an agent's .mcp.json)
npx -y @learning-with-court/cli@latest

Auth flow

lwc auth login (and any subcommand that needs a token) runs an authorization-code + PKCE flow against workshop.institute:

  1. The CLI starts a loopback server on an ephemeral localhost port and opens https://workshop.institute/cli-auth?... with a PKCE challenge and random state.
  2. You sign in (if needed) and click Authorize.
  3. The browser redirects to http://localhost:<port>/callback?code=..., the CLI exchanges the code at mcp.workshop.institute/cli/token, and caches the resulting JWT.

Tokens are RS256 JWTs signed by an AWS KMS key; the public key is published at https://mcp.workshop.institute/.well-known/jwks.json. Lifetime: 90 days. After expiry, re-run lwc auth login.

Environment overrides

  • LWC_TOKEN — bypass the cache and use this token directly.
  • LWC_API_URL — point at a different MCP API origin (default https://mcp.workshop.institute).
  • LWC_LANDING_URL — override the browser-side landing origin (default is derived from LWC_API_URL: mcp. and mcp- prefixes are stripped, so mcp-dev.workshop.institutedev.workshop.institute).

Token storage

~/.lwc/token.json, mode 0600. Contains the JWT, expiry, and the opaque user identifier. Delete the file or run lwc auth logout to revoke locally.