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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sasva/llm-info

v1.0.11

Published

Information and utilities for various LLM providers

Readme

@sasva/llm-info

A lightweight package providing information about various Large Language Models (LLMs), including embedding, reranking, and other models.

Whereas @sasva/openai-adapters is responsible for translation between API types, @sasva/llm-info is concerned with

  • Templates
  • Capabilities (e.g. tools, images, streaming, predicted outputs, etc.)
  • Model aliases

and openai-adapters might depend on llm-info for some of these things.

Goal

We know we are done when the steps required to add support for a new model in Sasva are exactly

  1. editing a single LlmInfo object, and
  2. adding it to the supporting ModelProviders.

Code structure

The two primary types are LlmInfo and ModelProvider

Models are defined on their own in the models directory. They can be grouped however makes sense.

Providers are defined in the providers directory, with all models that they support in their models attribute. It's important that models are tied to providers, because the model might have slightly different attributes (e.g. context length) per provider. Define as much as possible in the base object, and then spread to update for the specific providers as needed.

Where to use llm-info

  • Replace autodetect.ts
  • See usage in BaseLLM constructor, and finish the job of using llm-info everywhere relevant.
  • Replace gui/pages/AddNewModel/configs/[providers/models].ts