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

@rulegate/adapter-kit

v0.3.0

Published

Public adapter contract and test harness for Rulegate adapters.

Readme

@rulegate/adapter-kit

The public contract for Rulegate adapters. An adapter turns one canonical set of AI-agent instructions into one tool's native config, and it is a pure module: { detect, read, write, docs }, no network, no writes.

This package is the contract. @rulegate/core is not — it is published because this package depends on it, but it carries no compatibility guarantee, and adapter source may not import it.

import {
  ADAPTER_API_VERSION,
  detected,
  finalizeArtifact,
  renderConcatenated,
  selects,
  sortRules,
  withHtmlMarker,
  type Adapter,
  type AdapterContext,
  type Artifact,
} from '@rulegate/adapter-kit';

Two entry points:

  • @rulegate/adapter-kit — the frozen contract.
  • @rulegate/adapter-kit/testing — the fixture harness, for tests only. It reads the filesystem, which is why it is not part of the contract entry.

Stability

The surface is frozen at API v1. Adding an export is non-breaking; removing or renaming one, or changing an existing shape, requires an ADAPTER_API_VERSION bump.

The full list, the breaking/non-breaking policy, and how a v2 would arrive are in docs/adapter-api-v1.md. Both halves are enforced by tests rather than by review: test/public-api.test.ts pins the export names and kinds, and test/shape/pins.ts pins the structural shapes that no export name would reveal.

MIT.