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

@b-tec/osp

v0.1.1

Published

The OSP command line: sign in, connect Claude Code and Codex, and read your storage facilities from a terminal.

Readme

OSP command line

OSP runs self-storage facilities. This is its command line: sign in once, then look things up from a terminal, and let coding agents such as Claude Code and Codex work in OSP as you.

npx @b-tec/osp setup

Setup opens your browser to approve the sign-in, adds tab completion, and connects Claude Code and Codex if you have them. It needs Node.js 20 or later.

To keep osp around rather than running it through npx each time:

npm install -g @b-tec/osp

What it does

osp setup                  Sign in, add tab completion, connect Claude Code and Codex
osp login [--no-browser]   Sign in by approving in a browser
osp logout                 Sign out here and on the server
osp status                 Who you are signed in as, and where

osp facilities             The facilities you can see, and your role at each
osp units [search]         Units, with --status available|occupied|overlocked|unrentable
osp occupancy              How many units are in each status
osp tenants [search]       Find tenants by name, phone or email
osp tenant <name or id>    One tenant: contact details, units and balance
osp ledger <name or id>    A tenant's ledger, unit by unit
osp owes                   Who is behind, oldest first
osp eod                    The end-of-day report (--date YYYY-MM-DD)

osp agents                 Connect Claude Code and Codex to OSP again
osp mcp                    Run OSP's tools for an agent over stdio (agents start this)

Every command takes --json for scripts, and --facility <name or id> where it makes sense.

Signing in

osp login opens OSP in your browser. Approve there, and the command line is signed in as you: it can do exactly what you can do in OSP, with the access you have at the time. If your role changes, so does its; if your account is deactivated, it stops working.

On a machine with no browser, osp login --no-browser prints a link to open on any device, and you paste back the code it shows.

The sign-in is kept in one file readable only by you (~/.config/osp, or %APPDATA%\osp on Windows). osp logout signs it out on the server and deletes the file. You can also sign out any sign-in from OSP under Settings, Command line.

Agents

Setup registers osp mcp with Claude Code and Codex. The agents start it themselves, and it passes their requests to OSP using your sign-in, so no key is copied into their settings. Everything they do is recorded under your name, and OSP's approval rules for agents apply: giving money back above your company's threshold, or beyond the day's agent budget, waits for an owner.

Another server

The command line talks to https://osp.b-tec.org unless told otherwise:

osp login --server https://your-osp.example.com

or set OSP_SERVER.