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

@pewterzz/karp

v1.0.4

Published

Local-first LLM CLI for instant command recall

Readme

karp

A local-first CLI that recalls shell commands using a local LLM. Ask in plain English, get back the exact command — nothing else.

karp "how do I check disk usage"
# df -h

No cloud. No subscriptions. Runs against any llama.cpp or Ollama server.


Requirements

  • Node.js 18+
  • A running llama.cpp or Ollama instance (local or on your network)

Install

npm install -g @pewterzz/karp

Setup

Point karp at your LLM server:

karp config url http://localhost:8080/v1/chat/completions
karp config model your-model-name.gguf

For Ollama, the URL is typically http://localhost:11434/v1/chat/completions.

Config is stored at ~/.karp/config.json.


Usage

Ask a question

karp "how do I recursively copy a folder"
# cp -r src/ dest/

The model returns only the command. If you include words like "explain" or "what does", it gives a one-sentence description instead.

Store a command

karp store "docker run -d -p 3000:8080 ghcr.io/open-webui/open-webui:main"

Stored commands are used as context when you ask questions. The more you store, the better karp gets at recalling your specific setup.

List stored commands

karp list
# 1. docker run -d -p 3000:8080 ghcr.io/open-webui/open-webui:main
# 2. df -h
# ...

Remove a stored command

karp remove 2

Repeat the last answer

karp last

Prints the previous response instantly — no LLM call.

View or change config

karp config                        # show all config
karp config url <url>              # set server URL
karp config model <model>          # set model name
karp config top_k <n>              # results sent to LLM (default: 10)
karp config threshold <n>          # store size before BM25 kicks in (default: 15)

How it works

Queries go to your local LLM with a strict system prompt that enforces command-only output. When your store grows past threshold entries, karp runs BM25 over your saved commands to find the most relevant ones before sending them as context — keeping prompts short and responses accurate.

All data lives in ~/.karp/:

| File | Purpose | |---|---| | config.json | Server URL, model, and tuning options | | commands.md | Your stored commands | | .last | Cache of the last response |


License

MIT