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

@bigsteele/the-fine-print

v0.1.0

Published

The fine print, read against the code. Reads what an app actually does (accounts, payments, trials, AI, uploads, pixels, texts, calls, testimonials, mobile builds) and lines it up against 49 US federal, state and app store rules, each with its law, its ex

Readme

The Fine Print

What your app does that the law cares about, and whether your fine print says so.

A compliance read, not legal advice.

npx -y @bigsteele/the-fine-print@latest            # Step 0 in the current repository
npx -y @bigsteele/the-fine-print@latest --skill    # install the Claude Code skill

What it does

Step 0, the scan (seconds, offline): reads the product's own files and lists

  • what the app does: accounts, payments, subscriptions and trials, cancellation, AI calls and chat, AI voice agents, uploads and public buckets, analytics, ad pixels, session recording, chat widgets, video, email, texts and calls, testimonials, income claims, iOS and Android builds, and sensitive data (health, biometrics, location, SSNs, financial);
  • who receives personal data: every vendor SDK and host it recognises, with what each one receives;
  • the fine print against the code: which data categories and vendors the privacy policy never mentions, and which expected clauses are missing;
  • which of the rulebook's rules that behaviour opens, and why, with file and line.

The read (THE-FINE-PRINT.md, a long agent session): grades every rule PASS, FAIL, UNKNOWN or N/A with evidence from the code, read-only probes of the live product, and a re-opened source for the law; writes The Fine Print - <App>.md with a verdict, the ship blockers, a fix for every failure (drafted policy text included), and the questions only the owner can answer.

The gate (--check): validates the grade and the deliverable mechanically. No verdict without every rule graded; no FAIL without a dated source; no "compliant" anywhere.

The rulebook

49 rules in src/rules.ts, US federal, state and app store: privacy notices and rights (CalOPPA, the 20 state privacy laws, account deletion), tracking (GPC and opt-out, CIPA session replay, VPPA), security of personal data, subscriptions (ROSCA, California's auto-renewal law), reviews and claims (FTC Part 465, endorsements, earnings, AI and compliance claims), AI (companion chatbot laws, bot disclosure, automated decisions), email, texts and calls (CAN-SPAM, TCPA, AI voices, recording consent), children and age (COPPA, app store age laws), sensitive data (health, biometrics), accessibility (ADA, Unruh, overlays), app stores (Apple and Google), terms (clickwrap) and regulated industries (credit repair, the Safeguards Rule).

Every source carries the month it was last checked. The scan flags any rule whose newest check is older than six months, and the read re-opens a source before recording any FAIL. When the law changes, update the rule and its checked month.

Use

npx -y @bigsteele/the-fine-print@latest [dir]               # Step 0: the scan, plus THE-FINE-PRINT.md
npx -y @bigsteele/the-fine-print@latest --check             # the gate, on a finished read
npx -y @bigsteele/the-fine-print@latest --ignore vendor-dir # skip code that is not the product
npx -y @bigsteele/the-fine-print@latest --skill             # install the Claude Code skill

Then open Claude Code in the repository and have it follow THE-FINE-PRINT.md, or just ask it to "run the fine print" once the skill is installed. Paths listed in .fineprintignore (one per line) are skipped, for vendored engines and reference copies.

Not covered: EU, UK and other non-US law; tax; industry licensing beyond credit repair.