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

@rnsk/bot

v0.0.4

Published

Embeddable Runstack chat widget with gooey UI, API-key auth, and toolkit/agent scoping.

Readme

@rnsk/bot

Embeddable Runstack chat widget with gooey expand/collapse UI, API-key authentication, and optional Studio agent / toolkit scoping.

Install

npm install @rnsk/bot

Peer dependencies: react, react-dom, ai, @ai-sdk/react.

Usage

import { RunstackBot } from '@rnsk/bot';
import '@rnsk/bot/styles/bot.css';

export function SupportBot() {
  return (
    <RunstackBot
      apiKey={process.env.NEXT_PUBLIC_RUNSTACK_API_KEY!}
      position="right"
      placeholder="Ask anything…"
      agentIds={['agent_xxx']}
      toolkits={['github']}
      systemPrompt="You are a helpful support assistant."
    />
  );
}

Props

| Prop | Type | Default | Description | | --- | --- | --- | --- | | apiKey | string | required | Runstack API key (rnsk_…) | | position | 'left' \| 'right' | 'right' | Corner anchor | | placeholder | string | 'Ask anything…' | Input placeholder | | agentIds | string[] | — | Scope tools to Studio agents | | toolkits | string[] | — | Scope tools to toolkit ids | | systemPrompt | string | — | Extra system instructions | | apiBase | string | https://app.runstack.engineer | API base URL | | theme | 'light' \| 'dark' \| 'system' | 'system' | Widget theme | | toolkitIndex | ToolkitIndexEntry[] | — | Extra toolkit display metadata (logo, name, tools) merged over the bundled index. Needed only when the backend serves toolkits newer than this package. |

Testing unreleased toolkits

The bot only renders the chat; tools run on whatever server apiBase points at. The rnsk-toolkits sandbox serves the same /api/bot/* contract backed by local toolkit source:

// toolkitIndex comes from the sandbox's GET /api/toolkit-index
<RunstackBot
  apiKey="sandbox"
  apiBase="http://localhost:5173"
  toolkits={['mathematics']}
  toolkitIndex={toolkitIndex}
/>

Model selection

The bot uses the workspace Bot model configured in Runstack settings (LLM Providers). It falls back to the workspace default model, then Runstack auto-default providers.

Security

API keys in browser bundles are visible to users. For production, proxy requests through your backend.