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

getopen

v0.4.0

Published

Open Analytics from the command line: install the tracking snippet with one command, then read your sites and stats from the terminal.

Vulnerabilities

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

Links

Git

Maintainers

uaghazadeuaghazade

Keywords

analyticsweb-analyticsprivacyopen-analyticscli

Readme

getopen

Open Analytics from the command line. One binary, zero dependencies, installs as oa.

npm i -g getopen    # installs the oa command
# or one-off, nothing to install:
npx getopen init

Install the snippet

oa init

Run it in your project folder. It detects the framework, asks for your tracking key, and writes the snippet where it belongs. Detected frameworks: Next.js (App and Pages Router), TanStack Start, React (Vite / CRA), Vue, Nuxt, SvelteKit, Remix, Astro, Gatsby, WordPress and plain HTML.

The edit is idempotent (running it twice reports "Already installed") and refuses with a named error rather than guessing when a file is not in a shape it can safely edit.

Read your data

oa login                              # connect this terminal to your account
oa sites                              # the sites you can read
oa stats --site my-site --json        # stats, machine-readable

Every read command takes --json for machine-readable output and --api <url> (or OA_API_URL) to point at your own deployment. Self-hosting? The same commands work against your install.

Exit codes are stable and documented in oa --help.

What's new in 0.4.0

  • oa init detects TanStack Start (React and Solid flavours) and writes the script entry into the root route's head(). Contributed by @DeckardGer.

Links

  • Docs: https://getopen.so/docs/cli
  • Source and self-hosting: https://github.com/OpenLabs-so/openanalytics

MIT © Voprex Labs