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

@scoutui/cli

v0.2.0

Published

Scan React and Vue repos for design-system component usage, and upload the results to a Scout dashboard.

Readme

@scoutui/cli

The CLI for Scout, the design-system adoption dashboard.

It scans a React or Vue repository, web components included, and records every component the code uses, where it's used and with which props. scout scan uploads that scan to a Scout dashboard, where you compare repos, track migrations and follow adoption over time.

Get started

You need Node 24 or later. Install the repo's dependencies first: the scan reads your files without running or building them, and follows imports into node_modules to find where each component comes from. Yarn projects need nodeLinker: node-modules.

npm i -D @scoutui/cli
npx scout init
npx scout scan --dry-run

init writes scout.config.json, and scan --dry-run writes scout-scan.json next to it without uploading. Scan your first repo explains the result.

Upload to a dashboard

Sign in once, then scan. scout scan checks that the dashboard can take the scan, then uploads it:

npx scout auth login --host https://scout.example.com
npx scout scan

In CI, use an upload token instead. See Run a scan and upload in CI.

Commands

| Command | What it does | | --- | --- | | scout init | Creates scout.config.json for the repo | | scout scan | Scans the repo and uploads the scan to the dashboard; --dry-run writes it to scout-scan.json instead | | scout backfill | Scans past commits on the tracked branch, one per week, and uploads them | | scout auth login, status, logout | Signs in to a dashboard, shows the sign-in, or ends it |

The CLI reference lists every flag, exit code and environment variable, and the config reference every field in scout.config.json.

Links

The package includes a CycloneDX software bill of materials at dist/sbom.cdx.json.