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

@uvaits/aigw

v0.6.6

Published

Connect Claude Code and Codex to the UVA AI Gateway with your Entra identity. No API keys on your machine.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

robbinsjd4robbinsjd4

Keywords

uvaai-gatewayclaude-codecodexentra

Readme

@uvaits/aigw

Use the University of Virginia's AI Gateway from Claude Code and Codex, signed in with your UVA (Entra) identity. No API key is ever created, copied, or stored on your machine.

npm install -g @uvaits/aigw
aigw connect --portal <portal-url> --client-id <id> --tenant-id <id> \
             --portal-scope api://<portal-app-id>/Launcher.Access

Copy that full command from the Connect tab of your gateway portal — it fills in the values for your institution. After the first run, aigw connect on its own is enough.

What it does

connect signs you in through your browser, shows the allocations you are rostered on, and writes an isolated tool config that points Claude Code or Codex at the gateway. Your personal ~/.claude and ~/.codex are never read or written.

From then on the tools handle their own credentials: they run aigw token every few minutes and immediately after any 401, and it returns a short-lived Entra access token from your operating system's protected credential store. Nothing long-lived is written to disk.

| Command | What it does | | --- | --- | | aigw connect | Sign in, choose an allocation, write the tool config | | aigw launch claude / codex | Start a tool against that config | | aigw status [--check] | What this machine is set up to do; --check asks the gateway whether your traffic actually arrived | | aigw disconnect | Sign out and remove what connect wrote | | aigw token | Print a gateway token — the tools call this, you rarely do |

Requirements

  • Node.js 20 or newer
  • An allocation on the gateway (ask on the portal if you have none — connect will link you there)
  • A working OS credential store: Keychain on macOS, DPAPI on Windows, libsecret on Linux (apt install libsecret-1-0 gnome-keyring). Tokens are never written to a plain file, so connect stops with instructions rather than falling back.

Security

No provider API keys and no gateway keys exist on your machine. The only stored credential is an Entra refresh token inside the OS credential store; access tokens live 60–90 minutes and are fetched on demand. Losing a laptop is handled by disabling the account — there is no key inventory to chase. Every file this tool writes contains endpoints and an allocation id, never a secret.

Full design: docs/npm-connect.md