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

@yanlinglabs/winter-provider-catalog

v0.0.53

Published

Winter's provider and model catalog as inert, validated DATA: 218 provider rows and 1298 model rows with their endpoints, auth kinds, pricing evidence, admission tier and provenance, plus the validator and the vocabularies the JSON Schema restates.

Readme

@yanlinglabs/winter-provider-catalog

Winter's provider and model catalog as inert, validated DATA: 218 provider rows and 1298 model rows with their endpoints, auth kinds, pricing evidence, admission tier and provenance, plus the validator and the vocabularies the JSON Schema restates.

No network, no filesystem, no Bun API — the catalog is a bundled JSON module import, which is what lets it be decoded anywhere. PROVENANCE.md records where every row came from and under what evidence; bun run provenance:tiers -- --check regenerates its census from the shipped data.

Install

This package is published to two registries, and which one you want depends on who you are.

From public npm (anyone)

npm install @yanlinglabs/winter-provider-catalog

Nothing else is needed: the @yanlinglabs scope is public on npm.

From GitHub Packages (the yanlingLabs org)

GitHub Packages needs the scope pointed at it and an authenticated read, even for a public package. In your project's .npmrc:

@yanlinglabs:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}

…with GITHUB_TOKEN in the environment — a personal access token carrying read:packages, never a literal in the file. Then npm install @yanlinglabs/winter-provider-catalog as usual.

The published packages contain COMPILED OUTPUT ONLY. Each tarball ships dist/ — the bundled JavaScript a consumer imports and the .d.ts declarations their type-checker reads — plus its data files, README.md and LICENSE. It does not ship src/: the TypeScript sources live at https://github.com/yanlingLabs/winter-agent-sdk, which is where to read them, file an issue, or send a patch.

License

MIT — see LICENSE, which ships in the published tarball.

This package's generated catalog data cites the Apache-2.0 licensed xai-org/grok-build as the source for several xAI model-catalogue rows; that attribution is in NOTICE — identical to the root NOTICE — which ships in the tarball beside this file.

The separate OmniRoute-corpus extraction this package's catalog data is built from (no code copied, two licence/notice files registered verbatim under third_party/) is documented in PROVENANCE.md, which also ships in the tarball.