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

@waken/sdk

v0.1.1

Published

Waken SDK: persistent AI agents hosted on the cloud, from TypeScript and JavaScript

Readme

@waken/sdk

Persistent AI agents hosted on the cloud, from TypeScript and JavaScript. A thin client over the Waken HTTP API, no dependencies, Node 18+, Deno, Bun and browsers.

npm install @waken/sdk
import { Waken } from "@waken/sdk";

const waken = new Waken({ apiKey: process.env.WAKEN_KEY! });

const agent = await waken.agents.create({
  name: "bookkeeper",
  model: { provider: "anthropic", api_key: process.env.ANTHROPIC_API_KEY! },
  spend_cap_usd: 10,
});

const reply = await waken.agents.message(agent.id, "Sort my March receipts by vendor.");
console.log(reply.text);

const cp = await waken.checkpoints.take(agent.id);   // a point you can rewind to
await waken.checkpoints.restore(agent.id, cp.id);      // rewind: files, memory, conversation

Everything the API does is here: agents (create, list, get, delete, message, sleep, wake, restart, usage, resize, setModel, setHarness, logs, exec), checkpoints (take, list, restore), files (list, read, readText, write, mkdir, move, delete, uploadTar), env (list, set), triggers (schedules and the agent's incoming webhook), webhooks (events on all your agents), harnesses(). Any other route: waken.request(method, path, body).

Errors throw a WakenError with status and the API message.

Keys are created in the dashboard, Developers. An agent runs on your own model key, passed at creation and never stored by Waken.