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

ns-omp-provider-kiro

v0.4.0

Published

OMP (oh-my-pi) provider plugin: adds Kiro (AWS CodeWhisperer/Q) models via your kiro-cli login

Readme

ns-omp-provider-kiro

Kiro (AWS CodeWhisperer/Q) models in OMP.

Published on npm as ns-omp-provider-kiro:

omp plugin install ns-omp-provider-kiro

Pin a version with omp plugin install [email protected] — bare names, scoped names, and name@version all resolve as npm specs.

From a local build

To build from a clone instead — for developing this package or ns-kiro-core before a release — install from the path:

git clone [email protected]:ngosangns/ns-bridge.git
cd ns-bridge && pnpm install && pnpm -r build
omp plugin install ./packages/omp-provider-kiro

Sign in once with kiro-cli — Builder ID, IAM Identity Center, Google, GitHub, or enterprise OIDC all work, because kiro-cli does them:

kiro-cli login

Then, in OMP:

/login kiro
/model

/login kiro picks up the kiro-cli session and refreshes it when it expires, writing the refresh back so both tools stay on the same token. With no session on the machine it prompts for a Kiro API key (ksk_…) instead.

/model lists whatever your account's region actually serves: the catalog is fetched from Kiro's management API and cached for an hour, so a model added upstream shows up without a release here.

Notes

  • Reasoning effort maps onto Kiro's own ladder per model — xhigh and max exist only where the model advertises them, and a request for more thinking than a model offers is clamped rather than rejected.
  • Usage (/settings) reports the account's Kiro credit balance — the one the host is signed in with, so run /login kiro after signing the machine into a different account.
  • Sessions come from the machine: the kiro-cli store first, the Kiro IDE's token file as a fallback. They can be different IdC users of the same Kiro profile, so KIRO_AUTH_SOURCE=ide switches a machine over to the IDE's login instead.
  • KIRO_API_KEY is read as a fallback when no session is stored.
  • KIRO_DEBUG=1 writes a full request/response trace to ~/.ns-kiro-provider/logs/kiro-debug.log, with credentials redacted.

This is the recommended Kiro path in OMP. ns-omp-provider can also register a kiro provider, but leaves it off by default so the two never fight over the id.

Part of ns-bridge.