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

@plurnk/plurnk-models

v3.0.0

Published

Release-time snapshot of Models.dev provider and model metadata for PLURNK.

Readme

@plurnk/plurnk-models

A release-time snapshot of provider and model metadata from Models.dev. @plurnk/plurnk-providers uses it to construct cataloged providers and resolve model facts without a Models.dev request during installation or runtime. Clients may use the same snapshot for model discovery.

Data

The generated snapshot retains only the facts PLURNK consumes:

| Lookup | Snapshot facts | | ------------------ | ---------------------------------------------------------------------- | | lookupProvider() | Provider id, AI SDK package, credential names, and optional API URL. | | lookup() | Context window, optional output limit, reasoning flag, and USD prices. |

Model entries without a positive context window are omitted. reasoning: true means the source asserted that capability; absence does not activate or disable runtime reasoning. A missing cost means Models.dev supplied no complete input/output rate pair.

import { lookup } from "@plurnk/plurnk-models";

const info = lookup("openrouter", "deepseek/deepseek-v4.1-flash");
// → {
//     contextWindow: 1_048_576,
//     maxOutputTokens: 393_216,
//     reasoning: true,
//     cost: {
//       inputPer1M: 0.15,
//       outputPer1M: 0.6,
//       cacheReadPer1M: 0.003,
//     },
//     …
//   }
// miss → null

provider is the PLURNK provider name. model is the provider-native id; for relays this is commonly publisher/model. resolveModel() also accepts an unambiguous provider-native suffix. catalogSnapshot() and providerCatalogSnapshot() expose the complete read-only maps.

Resolution boundary

This package owns snapshot generation and lookup, not runtime precedence. Context windows, output envelopes, reasoning activation, and prices resolve by different rules in the provider contract ({§model-fact-resolution}). In particular, PLURNK does not fetch live per-token prices.

Build and refresh

The lockfile selects Models.dev's official @opencode-ai/models/snapshot as a build-only dependency. Normal build and prepack generate the pruned source JSON and include it in dist; generated JSON stays out of Git. Generation works offline after dependency installation, and consumers need no upstream SDK.

To refresh the catalog from the repository root:

npm install --save-dev @opencode-ai/models@latest --workspace plurnk-models --no-audit --no-fund
npm run build --workspace plurnk-models
npm test --workspace plurnk-models

Commit the dependency/lockfile change, not the generated catalogs. npm run generate --workspace plurnk-models regenerates from the already installed snapshot without selecting a newer version. See {§model-catalog-build} and {§model-catalog-projection}.