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

test-gap-client

v1.0.0

Published

CLI tool for testing Gap proxy header injection

Readme

test-gap-client

A simple CLI tool to verify Gap proxy header injection is working correctly.

Prerequisites

  • Gap installed and running
  • Node.js 18+

Install

git clone https://github.com/mikekelly/test-gap-client.git
cd test-gap-client
npm install

Setup

1. Install the test-gap plugin

gap plugin install mikekelly/test-gap

2. Configure credentials

The test-gap plugin requires two credentials:

gap credential set mikekelly/test-gap apiKey
# Enter a test value, e.g., "foobar"

gap credential set mikekelly/test-gap clientId
# Enter a test value, e.g., "bazqux"

3. Create an agent token

gap token create test-agent
# Note the token (e.g., gap_19bfb04eb35)

Usage

npx ~/code/test-gap-client --gap-token <your-token>

Or with a custom proxy URL:

npx ~/code/test-gap-client --gap-token <your-token> --proxy-url https://localhost:9443

Expected Output

If everything is configured correctly, you should see the echo server response with injected headers:

{
  "headers": {
    "Host": "echo.free.beeceptor.com",
    "User-Agent": "test-gap-client/1.0.0",
    "Via": "1.1 Caddy",
    "X-Api-Key": "foobar",
    "X-Client-Id": "bazqux",
    "Accept-Encoding": "gzip"
  }
}

The X-Api-Key and X-Client-Id headers are injected by the Gap proxy via the test-gap plugin.

How it works

  1. The client connects to the Gap proxy (default: https://localhost:9443)
  2. Authenticates using Proxy-Authorization: Bearer <token> header
  3. Makes a request to https://echo.free.beeceptor.com through the proxy
  4. Gap matches the request to the mikekelly/test-gap plugin (which matches echo.free.beeceptor.com)
  5. The plugin injects X-Api-Key and X-Client-Id headers from stored credentials
  6. The echo server returns all headers, proving injection worked

Troubleshooting

"Could not load Gap CA" - Make sure Gap has been run at least once. The CA is exported to ~/Library/Application Support/gap/ca.crt on first run.

"Missing Proxy-Authorization header" - Ensure you're passing --gap-token with a valid token.

No injected headers - Verify the plugin is installed (gap plugin list) and credentials are configured (gap credential list mikekelly/test-gap).