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

oharness

v0.8.0

Published

A model-agnostic agent harness: swappable providers, tool calling, MCP, subagents, compaction, hooks and permissions.

Downloads

1,481

Readme

oharness

A model-agnostic agent harness for the terminal, built the way Claude Code is: the agent loop, tool execution, context management and permissions are one layer, and the model is a replaceable backend.

npm install -g oharness
export ANTHROPIC_API_KEY=sk-ant-...   # or OPENAI_API_KEY / GEMINI_API_KEY
oharness

Three commands are installed:

| | | |---|---| | oharness | the terminal UI — streaming output, permission prompts, slash commands | | oharness-headless | no UI, no prompts, JSONL on stdout and nothing else | | oharness-web | a browser frontend on localhost |

Switching model mid-conversation (/model sonnet → /model gemini) converts no history, because the history was never held in a vendor's shape.

With no UI there is nobody to ask. oharness-headless denies any call that would need a prompt and reports why — letting them through silently would make an unattended run more dangerous than a watched one, which is backwards. Grant what it needs with permission rules up front, or pass --permission-mode auto deliberately.

Documentation, architecture and the reasoning behind both: https://github.com/Jet1217/OHarness