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

@protoscan/cli

v0.2.1

Published

CLI tool for automated Figma prototype QA.

Downloads

1,085

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

oxxoprooxxopro

Keywords

Readme

@protoscan/cli

Command-line interface for ProtoScan — automated Figma prototype QA.

npx @protoscan/cli scan YOUR_FILE_KEY

Quick start

# Set your Figma token
export FIGMA_TOKEN=your_token_here

# Scan a prototype
npx @protoscan/cli scan YOUR_FIGMA_FILE_KEY

# HTML report
npx @protoscan/cli scan FILE_KEY --format html --output report.html

# Pass token inline
npx @protoscan/cli scan FILE_KEY --token figd_xxxx

# Full Figma URL
npx @protoscan/cli scan "https://www.figma.com/design/abc123/My-App?node-id=7-2"

Options

protoscan scan <file-key-or-url>

  -t, --token <token>          Figma token (or set FIGMA_TOKEN env var)
  -f, --format <format>        terminal | json | html  (default: terminal)
  -o, --output <path>          Write output to file
  --min-touch-target <px>      Minimum touch target size (default: 44)
  --skip <checks>              Comma-separated checks to skip
  --pages <ids>                Comma-separated page IDs to scan
  --simulate                   Run Playwright E2E simulator
  --record [dir]               Record simulator walkthrough video (.webm)
  --upload                     Upload HTML report to GitHub Gist
  --vision                     Run GPT-4o vision analysis (requires OPENAI_API_KEY)
  --max-vision-cost <usd>      Max spend on vision analysis (default: 5)

CI/CD

Exits with code 1 if critical or high issues are found.

Related packages

License

MIT