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

@web-axag/shim

v1.1.0

Published

A WebMCP registry for browsers that don't have one yet, so AXAG code runs unchanged

Readme

@web-axag/shim

A document.modelContext for browsers that don't have one yet, so code written against WebMCP runs unchanged.

npm install @web-axag/shim
import { installShim } from '@web-axag/shim';

installShim(); // no-op where the browser has its own implementation

Then register as usual — @web-axag/webmcp and the framework bindings find the shim exactly as they find a native implementation:

registerManifest(tools, { signal: route.signal, handlers });

What it is, and isn't

It implements the part of the draft a page calls: registerTool(tool, { signal }), with abort unregistering. It keeps the registered tools somewhere a bridge or an inspector can read them.

Installing it connects no agent. It is the socket a connection plugs into — @web-axag/bridge is one such connection.

Reading the registry

import { getShimRegistry } from '@web-axag/shim';

const registry = getShimRegistry();
registry?.listTools();                       // what is registered right now
registry?.subscribe(tools => render(tools));  // called whenever that changes
await registry?.callTool('order_track', { order_id: 'o1' });

Under 2 KB gzipped, with no dependencies: this is the one piece that ships on every page.