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

@iterium/sdk

v0.1.0

Published

Official TypeScript SDK for Iterium — chat with the autonomous Scrum Master agent, pull live stats, manage the Add-ons waitlist, and connect your own AI SDK agent to any MCP server.

Readme

@iterium/sdk

Official TypeScript client for Iterium — talk to your autonomous Scrum Master agent, pull live workspace stats, and manage the Add-ons waitlist from your own code, scripts, or backend.

Install

Inside this monorepo it's already linked as a workspace package. Standalone:

npm install @iterium/sdk

Quick start

import { IteriumClient } from "@iterium/sdk";

const iterium = new IteriumClient({
  baseUrl: "https://my-team.vercel.app", // your Iterium deployment
  workspaceId: "TENANT-99X",             // your Slack workspace / tenant id
});

// Talk to the agent — same tool loop as the dashboard Terminal and Slack.
const answer = await iterium.chat({
  messages: [{ role: "user", content: "Analiza el ticket Jira PROJ-1" }],
});
console.log(answer);

// Stream the response token-by-token instead.
for await (const delta of iterium.chatStream({
  messages: [{ role: "user", content: "Revisa el PR #234 de GitHub" }],
})) {
  process.stdout.write(delta);
}

// Structured sprint report.
const sprint = await iterium.getSprintSummary(
  "Sprint 42 del equipo Backend, 3 días restantes, PROJ-100 bloqueado por QA"
);
console.log(sprint.overallHealth, sprint.blockers);

// Live dashboard stats.
const stats = await iterium.getStats();

// Add-ons marketplace.
const { modules, requested } = await iterium.listAddons();
await iterium.toggleAddonWaitlist("qa");

API

| Method | Description | | --- | --- | | chat({ messages }) | Sends a message to the agent, returns the full text response. | | chatStream({ messages }) | Same, but an AsyncGenerator<string> yielding text deltas as they arrive. | | getSprintSummary(prompt) | Structured { velocity, blockers, recommendations, ... } sprint report. | | getStats() | Live workspace stats (messagesToday, blockersResolved, computeUsed, cacheHitRate). | | listAddons() | The Add-ons catalog plus which ones this workspace already requested. | | toggleAddonWaitlist(addonId) | Joins/leaves an Add-on's waitlist. |

All requests are scoped by workspaceId; pass a per-user userId too if you want per-user attribution in Iterium's logs.

Errors throw IteriumApiError with a .status (HTTP status code) you can branch on.

Build

pnpm --filter @iterium/sdk build