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

awaitful

v0.1.0

Published

Awaitful - earn from your AI coding agent's wait time. https://awaitful.com

Downloads

303

Readme

awaitful

One command to set up Awaitful: earn from your AI coding agent's wait time. When your agent (Claude Code and others) is thinking, Awaitful shows a single tasteful, clickable sponsored line in your editor, and you earn a share of what the advertiser paid.

npx awaitful

The installer finds your editor, runs <editor> --install-extension awaitful.awaitful, and tells you the one step left: run "Awaitful: Sign In" from the Command Palette. That is the entire job. Your editor downloads the extension from its own marketplace, and keeps it updated the same way it updates everything else.

Supported editors

| Editor | Detected as | Extension comes from | | ---------------- | --------------- | -------------------- | | VS Code | code | VS Code Marketplace | | Cursor | cursor | Open VSX | | Windsurf | windsurf | Open VSX | | VSCodium | codium | Open VSX | | VS Code Insiders | code-insiders | VS Code Marketplace |

Editors are found on your PATH first, then in their usual install locations (so a Mac without the code shell command still works).

npx awaitful                      # one editor found: installs; several: asks
npx awaitful --editor cursor      # no prompt
npx awaitful --all                # every detected editor
npx awaitful --dry-run            # print the exact commands, run nothing
npx awaitful status               # where is Awaitful installed, and which version

What this package will never do

  • No network requests. The installer never talks to the network itself; only your editor downloads anything, through its own marketplace channel. This is enforced by a test that fails the build if a network primitive ever appears in the shipped source.
  • No dependencies. Zero, enforced by the same test file. What you install is what you can read in a few minutes: the source.
  • No tracking. It does not know or report whether you ran it.

The extension itself makes the same kind of promises with the same kind of receipts. What leaves your machine, field by field: PRIVACY.md. It never reads your code, prompts, files, or your agent's output.

Manual install

No npm handy, or you would rather not run an installer at all:

Or from any of those editors directly: search "Awaitful" in the Extensions view.

Troubleshooting

"No supported editor was found" - your editor's CLI is probably not on the PATH. In VS Code open the Command Palette and run "Shell Command: Install 'code' command in PATH" (Cursor, Windsurf and VSCodium have equivalents), or install manually with the links above.

Several editors, non-interactive shell - pick one explicitly: npx awaitful --editor code, or take them all: npx awaitful --all.

Development

node --test          # the suite, including the no-network and no-dependency receipts
npx tsc -p .         # typecheck (checked JavaScript, no build step)

Issues: github.com/Awaitful/awaitful/issues

MIT (c) Awaitful