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

terrain-scout

v0.1.0

Published

Contract-only repo extractor for terrain-skin intake. Runs locally: uploads schema shapes, endpoint signatures, and UI vocabulary — never your source code.

Readme

terrain-scout

Contract-only intake extractor for a terrain skin. Runs locally in your repository. Your source code never leaves your machine.

npx terrain-scout --key <intake-key>

What it uploads

  • Schema shapes (Prisma models, SQL CREATE TABLE DDL, model field names)
  • Endpoint signatures (POST /api/orders — route and method, never the handler)
  • Type/interface/enum declarations
  • UI vocabulary (the labels your interface already shows its users)
  • A two-level directory outline, your README's opening, dependency names

What it never uploads

Function bodies, implementation code, credentials, data, file contents. Extraction happens on your machine; only the shapes above are sent.

Trust, verifiable

The full artifact is written to .terrain-scout/artifact.json before anything is uploaded — open it and read exactly what would leave. Nothing is sent until you confirm (or pass --yes). --dry-run extracts without uploading at all.

npx terrain-scout [dir]              # extract + confirm + upload
  --key <key>        intake key from your studio contact (or TERRAIN_SCOUT_KEY env)
  --note "..."       optional color: what piles up, what you wish you could see
  --dry-run          extract locally, upload nothing
  --yes              skip the confirmation prompt
  --server <url>     override the intake server

After upload you get back the domain brief — what the studio understood about your operation from the shapes alone. If it reads wrong, say so; the brief drives the design.

Node 18+. Zero dependencies.