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

@nothumanwork/wit-sdk

v0.1.0

Published

Zero-dependency TypeScript client for the wit URL API (read GitHub repositories without cloning).

Readme

@nothumanwork/wit-sdk (TypeScript)

Zero-dependency client for the wit URL API: read any GitHub repository without cloning, with token budgets you control. Works anywhere fetch exists (Node 18+, Deno, Bun, Workers, browsers).

import { WitClient } from "@nothumanwork/wit-sdk";

const wit = new WitClient({ token: process.env.GITHUB_TOKEN });
const repo = wit.repo("ratatui/ratatui"); // or wit.repo("o/r", "v0.29.0")

const stats = await repo.stats();                          // size / tokens / languages, no blob reads
const files = await repo.rgFiles("impl Widget for", { glob: "*.rs" });
const outline = await repo.outline(files.files[0].path);   // symbols with line ranges
const impl = outline.symbols.find((s) => s.kind === "impl");
const code = await repo.cat(files.files[0].path, { lines: [impl.line, impl.end_line] });
console.log(code.commit, code.text);                       // provenance travels with every result

Higher-level helpers that chain calls for you:

  • repo.readSymbol(path, name, { kind, padding }) → outline + cat range (2 requests).
  • repo.context(pattern, { window, maxSnippets, glob }) → rg + one cat window per file.
  • wit.search({ query: "terminal ui", lang: "rust" }) → find owner/repo first.
  • repo.text("tree", { path: "src", l: 1 }) → the CLI-identical plaintext for any verb.

Errors are WitError with status, code, retryAfter and isRateLimited; pass retries: 2 to have 429s retried while honouring retry-after.

Develop

cd sdk/typescript
npm run check        # tsc --noEmit + node --test (Node 22+ strips types natively)
npm run build        # emits dist/ for publishing

Release

.github/workflows/publish-sdk.yml publishes to npm on every push to main that touches sdk/typescript/ when package.json's version is not on the registry yet (it uses the repository's NPM_TOKEN secret). To release: bump version, merge, done. Pushes that leave the version unchanged run the checks and skip the publish. workflow_dispatch with dry_run rehearses a release without publishing.