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

@rurout/opencode-v1

v0.2.2

Published

OpenCode 1.x provider plugin for RuRout — live model discovery from your gateway key.

Readme

@rurout/opencode-v1

OpenCode 1.x provider plugin for RuRout — your gateway key becomes a first-class provider in /models.

For OpenCode 2.x, use @rurout/opencode-v2 instead.

What the client gets

  • New RuRout provider in the OpenCode model picker, next to the built-ins.
  • Model list discovered live from GET /v1/models with the active key — each client sees exactly the models that key allows.
  • Provider and model names include the admin-given key name from GET /v1/sub2api/billing (e.g. RuRout Germes).
  • /connect rurout stores the key in OpenCode's auth system.
  • The active key is checked on startup and hourly without a restart. A successful refresh replaces the list, including removing models unavailable to the key. Stale ~/.cache/opencode-rurout/models-*.json files are deleted on startup.

Install (OpenCode 1.x only)

opencode plugin add @rurout/opencode-v1@latest

Then inside OpenCode:

/connect

Select rurout, paste the gateway API key. Restart OpenCode, then /models → pick a rurout/* model.

Environment alternative (servers / CI):

export RUROUT_API_KEY=sk-...
opencode

Custom gateway address

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@rurout/opencode-v1@latest"],
  "provider": {
    "rurout": {
      "options": {
        "baseURL": "https://your-gateway.example.com:9443/v1"
      }
    }
  }
}

Or export RUROUT_BASE_URL=....

How it works

The v1 config hook registers the rurout provider with @ai-sdk/openai-compatible, fetches GET /v1/models with the active key, preserves the exact IDs returned by the gateway, and fills in context/pricing metadata. The auth hook adds /connect rurout.