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

badgr-run-action

v1.0.0

Published

GitHub Action adapter for bounded remote execution through existing Badgr Jobs

Readme

badgr/run

badgr/run@v1 is the GitHub Action mapping for Badgr's small Remote Execution Adapter contract. Agent-toolkit is adapter proof number one; this Action is adapter number two. GitHub supplies the trigger and repository context, then the Action translates that context into the existing POST /v1/run lifecycle.

Adapter proof number one maps a loop without changing the execution primitive:

repository + exact ref + GitHub token + LLM key
→ agent-toolkit loop run daily-triage
→ POST /v1/run
→ existing logs, evidence, receipt, and teardown
- uses: badgr/run@v1
  with:
    command: npx playwright test
    max-cost: 2
    max-runtime: 30
    github-token: ${{ github.token }}
  env:
    BADGR_API_KEY: ${{ secrets.BADGR_API_KEY }}

The Action does not implement execution, routing, billing, or teardown. Those remain part of Badgr Jobs.

Use github-token (or GITHUB_TOKEN in the step environment) when the source repository is private. The token is masked and forwarded to the worker for checkout as BADGR_GITHUB_TOKEN.