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

@snagtag/cli

v0.2.1

Published

Command-line tool for managing SnagTag test reports.

Readme

@snagtag/cli

Command-line tool for managing SnagTag test reports.

Install

npm install -g @snagtag/cli
# or use npx
npx @snagtag/cli fetch

Configuration

Create snagtag.config.json in your project root:

{
  "adapter": "supabase",
  "supabaseUrl": "https://your-project.supabase.co",
  "serviceRoleKey": "your-service-role-key",
  "tenantId": "optional"
}

Or use environment variables: SNAGTAG_SUPABASE_URL, SNAGTAG_SERVICE_ROLE_KEY, SNAGTAG_TENANT_ID.

Also checks .env.local for VITE_SUPABASE_URL as fallback.

Commands

Fetch reports

snagtag fetch                              # All submitted reports
snagtag fetch --status submitted,in_progress  # Include in-progress
snagtag fetch --severity blocking          # Only blocking issues
snagtag fetch --limit 10                   # Cap at 10
snagtag fetch --no-mark                    # Don't mark as in_progress
snagtag fetch --dry-run                    # Preview without changes

Downloads screenshots to /tmp/snagtag-reports/ and outputs markdown to stdout.

Mark reports

snagtag mark-fixed TR-47,TR-51 --commit abc123 --notes "Fixed the query"
snagtag mark-wont-fix TR-48 --notes "Intentional behaviour"
snagtag mark-deferred TR-49 --notes "Post-launch"
snagtag reopen TR-50

Report refs accept both TR-47 and 47 formats.

Adapters

Works with all three backends:

{ "adapter": "supabase", "supabaseUrl": "...", "serviceRoleKey": "..." }
{ "adapter": "rest", "baseUrl": "https://api.example.com/snagtag" }
{ "adapter": "local", "dbName": "my-app" }

License

MIT