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

@kolkrabbi/kol-search

v0.3.0

Published

Search engine, custom built for wide use-cases

Readme

@kolkrabbi/kol-search

The KOL search engine. Plain ESM, no React, no DOM, no dependencies. Engine tier (ARCHITECTURE §3): the UI — an overlay, chips, a results page — lives in the UI packages and calls this.

import { createIndex, search } from '@kolkrabbi/kol-search'

const index = createIndex(items)                    // items: { id, title, kind?, space?, category?, tags?, headings?, keywords?, description?, body?, date? }
const { results, facets, query, total } = search(index, 'atom tag:pattern/input -legacy', { scope: { space: 'components' } })
results[0].reasons   // [{ term, field, rung, weight, hit? }] — why it ranked there
facets.category      // [{ value, count, selected }]
query.tokens         // how the box was read, for chips

The query language

| write | means | |---|---| | button | a text term — every term must match somewhere | | "exact phrase" | a text term, never read as a filter | | -legacy | must NOT match | | tag:layout · #layout | tag filter | | kind:doc · is:doc | kind filter | | space:docs · in:docs | space filter | | category:atoms · cat:atoms | category filter | | -tag:draft | exclude a facet value | | after:2026-09-01 · before:… | date bounds on item.date | | atom | smart term — a bare word naming a facet value (singular or plural) becomes that filter |

Filters are AND across fields, OR within one field.

Ranking

A term scores the best field it hits: title exact 100 · title prefix 60 · title word start 40 (camelCase splits: Anatomy in ColorAnatomy) · title contains 25 · tag exact 30 · tag contains 12 · heading 15 · keyword 10 · description 8 · body 3. Ties sort by title. WEIGHTS is exported.

Options

createIndex(items, { facets, smart, aliases }) — facets (default space · kind · category · tags) are counted; smart (default category · kind · space) feed smart terms, earlier wins a clash; aliases maps extra words to { field, value }.

Proved in apps/search.