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

@www.hyperlinks.space/program-kit

v123.123.123

Published

Hyperlinks Space Program

Vulnerabilities

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

Links

Git

Maintainers

Keywords

Readme

Program Kit

Program Kit is a production-ready cross-platform starter published from repository root. It is built around React Native + Expo and is designed to be quickly tested, scaled, and deployed across popular platforms.

What You Get

  • Expo + React Native app foundation
  • Telegram bot support (webhook + local bot scripts) with AI functionality
  • Telegram Mini App-ready client structure
  • Android and iOS clients
  • Windows desktop packaging (.exe) with Electron Builder
  • CI-oriented release workflow and deployment helpers
  • OpenAI functionality and Swap.Coffee for blockchain data retrievement

Install

npmjs (public)

npx @www.hyperlinks.space/program-kit ./new-program

GitHub Packages

npx @hyperlinksspace/program-kit ./new-program

If you install from GitHub Packages, configure .npmrc with the @hyperlinksspace registry and token.

After Scaffold

Copy npmrc.example to .npmrc so installs match this repo (legacy-peer-deps; npm does not ship a real .npmrc in the tarball for security):

cd new-program
cp npmrc.example .npmrc
npm install
npm run start

If you prefer not to use a .npmrc, you can run npm install --legacy-peer-deps instead of the copy step.

Then open the project fullREADME.md for details (env vars, bot setup, build and release commands).

Release Channels

  • latest for stable milestone snapshots
  • next for rolling preview snapshots

Notes

  • Published from the repository root; the pack includes everything except patterns in .npmignore (no files whitelist in package.json).
  • .npmrc cannot be published on npm; npmrc.example is included so you can copy it locally.

Matching local development

Use the same setup you would after cloning this repo:

  1. Node — Prefer the version in .nvmrc (aligned with package.json engines).
  2. npm install — Copy npmrc.example to .npmrc, then run npm install (same legacy-peer-deps behavior as a local checkout with a root .npmrc).
  3. Env — Copy .env.example to .env and fill variables (details in fullREADME.md after the CI readme swap, or in the main repo README).

The tarball does not ship package-lock.json (by .npmignore); the first install generates a lockfile for your machine, like cloning without a committed lock.