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

@coderifts/contract-path

v1.0.0

Published

Path-name classifier for API contract artifacts (OpenAPI, AsyncAPI, GraphQL, gRPC, MCP). Single list. Zero dependencies.

Readme

@coderifts/contract-path

Path-name classifier for API contract artifacts. Single list. Zero runtime dependencies.

This is the same classifier the CodeRifts merge gate and the generic derivation: "server" path (ID637 6b) use. Hosts (OpenAI-Agents guardrail, hooks, other packages) import it from npm instead of reaching into the app checkout.

Classification is path-name only. The module does not read file content.

npm install @coderifts/contract-path
const { looksLikeContractPath, typeForPath } = require('@coderifts/contract-path');
// or: import { looksLikeContractPath, typeForPath } from '@coderifts/contract-path';

if (looksLikeContractPath(filename)) {
  const type = typeForPath(filename); // 'openapi' | 'asyncapi' | 'graphql' | 'grpc' | 'mcp_manifest'
}

Call looksLikeContractPath first. typeForPath is a mapping, not a gate: typeForPath('package.json') returns 'openapi' even though looksLike is false.

What counts

A path is a contract artifact when all of:

  1. It is not under node_modules/ or vendor/.
  2. Its extension matches .(ya?ml|json|graphql|gql|proto) (case-insensitive).
  3. Its path-name contains openapi, swagger, asyncapi, or mcp, or the extension is .graphql / .gql / .proto.

| Path | looksLike | type (if looksLike) | |---|---|---| | api/openapi.yaml | true | openapi | | swagger.json | true | openapi | | asyncapi.yaml | true | asyncapi | | schema.graphql | true | graphql | | svc/user.proto | true | grpc | | mcp.json / .well-known/mcp.json | true | mcp_manifest | | package.json | false | — | | tsconfig.json | false | — | | package-lock.json / pnpm-lock.yaml | false | — | | .github/workflows/ci.yml | false | — | | README.md / src/index.js | false | — | | node_modules/openapi.yaml | false | — | | vendor/openapi.yaml | false | — |

Existing behaviour, not a new rule: .github/workflows/openapi.yaml is true today because the file name contains openapi. Do not invent a workflow exclusion in this module.

Dual module

CJS (index.cjs) is the algorithm. ESM (index.mjs) re-exports it via createRequire so there is one list, not two.