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

@krishantt/opencode-go-usage

v0.1.3

Published

OpenCode TUI plugin: OpenCode Go usage limits plus burn-rate pacing warnings in the status bar

Readme

@krishantt/opencode-go-usage

OpenCode Go usage limits — with burn-rate pacing — in the OpenCode TUI status bar.

GO r4% · w42% ⚠10h/2d · m21% ⚠3d/18d

Shows rolling / weekly / monthly quota consumption of the managed OpenCode Go provider, and warns when your current burn rate will exhaust a window before it resets.

Install

Requires OpenCode v2.2+ and the OpenCode Go provider. The numbers come from the OpenCode Console workspace your location is signed in to; an API key alone (no Console account sign-in) has no workspace to report and shows GO –.

{
  "plugins": ["@krishantt/opencode-go-usage"]
}

Restart the TUI. The indicator appears after its first fetch (up to a minute).

Reading the bar

Per window: r rolling (5h), w weekly, m monthly, as percent consumed.

| Glyph | Meaning | | --- | --- | | (none) | fine | | ▲ | window at ≥ 85% — nearly spent | | ! | window currently rate-limited; value shows →<time> until reset | | ⚠eta/reset | at your current pace this window hits 100% in eta, but only reset remains — plan accordingly | | GO ⋯ | first fetch in flight | | GO – | no usage reported: not signed in to a Console workspace | | GO ? | fetch failed, hung, or an unexpected payload; see debug below |

Pacing is linear extrapolation of your own usage (samples kept ~6 h in memory, rebuilds after a TUI restart) and only appears when exhaustion actually precedes the reset — otherwise the bar stays clean. Warns need ≥ 10 minutes of history per window; rolling warns only count your current 5h cycle.

Debug

Run /go-usage-debug in the prompt (also in the Ctrl+P palette) to toggle fetch logging to ~/.cache/opencode/go-usage-debug.log: raw response envelopes, errors with stacks, and toggle events. Off by default and resets to off on restart because it logs a couple of lines per poll.

Status bar placement

prompt.footer.status and home.footer.status via TUI plugin slots. These and context.client.experimental.usage.limits are OpenCode v2 internals and may change between releases — if the bar goes missing or shows GO ?, check this repo's issues and your ~/.local/share/opencode/log/opencode.log.

License

MIT