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

@theokit/cli

v1.0.0

Published

Developer CLI for @theokit/sdk — init, dev, inspect, eval. Adoption Roadmap #1.

Readme

@theokit/cli — theokit

Developer CLI for @theokit/sdk. Four subcommands at v1: init, dev, inspect, eval. Adoption Roadmap #1.

Install

# One-shot scaffold via npx (recommended for first use):
npx @theokit/cli init my-bot

# Or install globally:
pnpm add -g @theokit/cli
theokit --help

theokit init <project-name>

Scaffold a new agent project from a bundled template.

theokit init my-bot --template minimal
theokit init local-rag --template ollama-local
theokit init my-bot-tg --template telegram-bot

Templates:

  • minimal — smallest possible Agent.create + send + stream.
  • ollama-local — 100% local via Ollama (no remote API key).
  • telegram-bot — Telegram bot via @theokit/gateway + grammy.

Flags:

  • -t, --template <name> — template to use (prompts if omitted).
  • -f, --force — overwrite non-empty destination.
  • -y, --yes — skip prompts (CI mode).

theokit dev

Run your agent's entry point under tsx --watch.

theokit dev                      # auto-detects src/index.ts or package.main
theokit dev --entry src/bot.ts   # explicit entry
theokit dev --env .env.local     # custom env file (default: .env)

theokit inspect

List what the SDK sees: builtin providers, embedding adapters, gateway adapters, discovered plugins.

theokit inspect
theokit inspect --json                 # machine-readable
theokit inspect --filter providers     # narrow to one kind

theokit eval

Run a eval.config.{ts,mjs} against a real LLM and emit a markdown report.

theokit eval                              # ./eval.config.ts → ./eval-report.md
theokit eval --config my-eval.ts --output reports/run1.md

Example eval.config.ts:

import type { EvalConfig } from "@theokit/cli";

export default {
  dataset: [
    { input: "Say hello in one word.", expected: "hello" },
    { input: "What is 2+2?", expected: "4" },
  ],
  scorers: [
    {
      name: "contains-expected",
      score: (output, expected) =>
        typeof expected === "string" && output.toLowerCase().includes(expected.toLowerCase())
          ? { score: 1 }
          : { score: 0, reason: `expected "${expected}"` },
    },
  ],
  agent: {
    apiKey: process.env.THEOKIT_API_KEY ?? "local",
    model: { id: "ollama/llama3.2:3b" },
    local: { cwd: process.cwd() },
  },
} satisfies EvalConfig;

The eval runner v1 wraps Agent.batch (ADR D134); when Roadmap #2 ships, internals swap to Eval.run — your config keeps working.

Exit codes

| Code | Meaning | |---|---| | 0 | Success | | 1 | Unknown error | | 2 | User error (bad flags, validation failure, etc.) |

Architecture

See ADRs D193-D201 in .claude/knowledge-base/adrs/:

  • D193: separate workspace package
  • D194: commander routing
  • D195: bin name theokit
  • D196: bundled templates (offline-friendly)
  • D197: dev via tsx --watch
  • D198: inspect is read-only
  • D199: eval v1 wraps Agent.batch
  • D200: 3 initial templates
  • D201: Theokit.inspect.* public API

Requirements

  • Node 22.12+.
  • pnpm (recommended) or npm. Templates use pnpm scripts; npm/yarn users can manually translate.