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

audits-run

v0.0.3

Published

Command line client for Audits SEO reports, remote MCP setup, and agent workflows.

Readme

audits-run

Command line client for Audits.

npm install -g audits-run
audits login
audits commands --search "programmatic SEO"
audits command performance.pseo
audits run performance.pseo --payload '{"projectId":"<id>","days":90}' --wait --json
audits command monitoring.index_plan
audits run monitoring.index_plan --payload '{"projectId":"<id>"}' --wait --json
audits run monitoring.index_watch --payload '{"projectId":"<id>","inspectionLimit":25}' --wait --json
audits api-keys
audits report --project <id> --wait

The CLI signs in to Audits, connects to your account, and runs commands through the same hosted command surface used by the API and remote MCP server. It is a hosted API client only, not the local crawler or core analysis engine.

Use plural audits commands --search "<goal>" to find the targeted command first. Use singular audits command <id> to inspect one command's inputs. audits report is the broad crawl-backed report. For index monitoring, run monitoring.index_plan before monitoring.index_watch; the plan does not spend Google URL Inspection quota, while watch uses tracked quota and saved snapshots.

API keys are managed through hosted commands too:

audits api-keys create --name "MCP token"
audits api-keys revoke <token-id>

Set AUDITS_API_URL for local development:

AUDITS_API_URL=http://localhost:4330 audits commands