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

storepulse

v0.12.0

Published

storepulse CLI — App Store Connect + Google Play release monitor. Live versions, review states, rollout % and test tracks for all your iOS & Android apps in one terminal board.

Vulnerabilities

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

Links

Git

Maintainers

diokrdiokr

Keywords

app-store-connectgoogle-playgoogle-play-consoleapp-storetestflightrelease-monitorapp-releasemobile-devopsiosandroidclidashboardexpoeasreact-native

Readme

storepulse

One-glance release status for all your iOS & Android apps.

Which version is live? Which is stuck in review? What's on TestFlight? One command shows every app you manage — versions, review states, rollout percentages, test tracks — across App Store Connect and Google Play.

npx storepulse demo   # see the board with sample data — no credentials needed
  • 🔍 Read-only — never changes anything in either store
  • 🔐 Credentials stay on your machine — direct API calls, no server, no telemetry
  • 🧩 Built on @storepulse/core, embeddable in your own tools

Commands

npx storepulse            # release board for storepulse.config.json
npx storepulse init       # scaffold storepulse.config.json + .env templates here
npx storepulse demo       # the board with sample data — no credentials needed
npx storepulse snapshot   # the board as JSON (--demo, --out <file>)
npx storepulse serve      # local web dashboard (--demo, --port, --host, --refresh)
npx storepulse explain    # badge glossary (explain <state> for one state in depth)
npx storepulse doctor     # diagnose credentials & permissions (find the 401/403)

Every command accepts --lang ko|en (or STOREPULSE_LANG; falls back to your OS locale) to switch CLI messages between English and Korean.

serve binds to 127.0.0.1 by default — click a row for release notes, dates, and TestFlight expiry, and filter by OS/group with the chips at the top; each row also sums up its latest bundle (Latest: 2.5.0 (108)) and marks every channel ✓ (has it) or ▲ (behind). The JSON document written by snapshot (and served at /api/status) is specified in docs/snapshot-schema.md.

Expo user? Set EAS_TOKEN in .env and an easProjectId per app to link every store version to the EAS build (commit · profile · submission status) that produced it.

Real apps

  1. Run npx storepulse init — it scaffolds storepulse.config.json (app list) and a .env template in the current folder, never overwriting existing files, and git-ignores the credential files.
  2. Fill them in: your apps in the config, an App Store Connect API key and a Google Play service account in .env.
  3. Run npx storepulse.

Full step-by-step tutorial: https://diokr.github.io/storepulse/

Links

  • Website & tutorial: https://diokr.github.io/storepulse/
  • GitHub: https://github.com/dioKR/storepulse
  • License: MIT