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

teamshift

v0.1.4

Published

Run TeamShift agent teams from your terminal. Metered by usage — no model key of your own required.

Readme

teamshift

Run TeamShift agent teams from your terminal. Metered by usage — you do not bring your own model key, so a run costs you TeamShift credit rather than an Anthropic or OpenAI bill.

npx teamshift login
npx teamshift catalog                  # prebuilt teams you can add
npx teamshift add code-audit-swarm     # adds it to your workspace
npx teamshift run <team-id> "review services/api for auth mistakes"

teamshift teams lists callable teams, including teams you built yourself in the portal; teamshift agents lists callable individual agents. Keeping the two inventories separate prevents a large internal agent library from burying the teams a customer actually runs. add is idempotent — running it twice will not duplicate a team or overwrite edits you have made to it.

Parallel fan-out

The reason to reach for the CLI instead of the API: one command dispatches many prompts at once and reports what each one cost.

npx teamshift run <team-id> \
  -p "audit auth" -p "map the schema" -p "find dead code" --concurrency 3
STATUS     CHARGE  TIME  PROMPT
─────────  ──────  ────  ───────────────
completed  $1.20   4.1s  audit auth
completed  $1.20   4.0s  map the schema
completed  $1.20   4.0s  find dead code

3 run(s) · $3.60 total · 8.1s wall clock (12.1s if run one at a time)

--file prompts.txt reads one prompt per line. Concurrency is bounded (default 5) so a large batch does not trip the API's write rate limit. Completed runs print their scrubbed deliverable after the status table; --json includes it as the outcome's output field.

Already using Claude Code or Codex?

Prefer the MCP server — it exposes the same teams as tools inside your existing agent, with no second CLI to learn. Both install commands are in the portal under Programmatic setup.

Auth

TEAMSHIFT_API_KEY wins over the stored config, so CI never has to write a file. teamshift login writes ~/.teamshift/config.json at mode 0600. TEAMSHIFT_API_URL overrides the endpoint.

Exit codes

| Code | Meaning | | --- | --- | | 0 | every run completed and returned its deliverable | | 1 | usage/auth error, timeout, failed run, or missing deliverable | | 2 | out of credit — add credits and rerun |

Releasing

Published on npm as teamshift. To release: bump version, pnpm build, run the package tests, then npm publish --access public from this directory.