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

@rizal72/oc-git

v0.2.3

Published

The sidebar's repository state: branch, the three counts, ahead/behind; the three counts also in the footer while the repository is dirty

Readme

@rizal72/oc-git

The repository's state, in the terminal and in the desktop app: the branch, then what has something to commit — added, modified, untracked — then ahead/behind, which appears only when an upstream exists.

Each count is grey at zero and warning-yellow when it is not, so a clean repository reads quietly. The branch being behind its upstream is the one other warning: it is never a resting state, so it turns the status yellow even with nothing to commit. The plugin draws nothing outside a repository or on a machine without git.

Install

opencode plugin add @rizal72/oc-git

Or by hand, one line in ~/.config/opencode/opencode.jsonc:

"plugins": ["@rizal72/oc-git"]

Update

V2 checks package plugins at startup and never applies the update, so a package only moves when you ask:

opencode plugin check     # which of the installed packages are behind
opencode plugin update    # apply them, and let the server reload

Or install @rizal72/oc-plugin-updates: the count appears in a pill above the composer, with the update one click away.

TUI

A block in the sidebar. While the repository is dirty the three counts also appear in the prompt footer, where a narrow window has no sidebar left.

GUI

A pill above the composer, with the whole state in its label: desktop +0 ±1 ?1, then ↑1 / ↓2 at the end only when there is something to push or pull — a zero there says nothing. Its rows spell out what the figures are — added, changed, untracked — plus the upstream when there is one.

How it works

One read of git status --porcelain=v2 --branch every three seconds, from the server half, shared by both surfaces; a tick is skipped while the previous read is still running. Read-only: no hook, no git server, nothing written.

Requires OpenCode v2. TypeScript, no build step, no runtime dependencies.