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

@heartidentity/heartify

v0.2.0

Published

Deploy static builds to heartify (uploads to Cloudflare Pages, registers the deploy, gates it behind a session).

Readme

@heartidentity/heartify

Deploy a static build to heartify with a single command and a single credential.

The CLI:

  1. exchanges your hrty_ deploy token for a short-lived, project-scoped Cloudflare Pages upload token (brokered by heartify — you never hold a Cloudflare account credential),
  2. uploads the build's files directly to Cloudflare Pages (so there's no size limit at heartify), and
  3. registers the deploy with heartify, which creates the Pages deployment from the manifest, allocates a version index, and returns the gated preview URL.

Install

npm i -g @heartidentity/heartify
# or run ad-hoc: npx @heartidentity/heartify deploy ./dist -p <key>

From inside this monorepo, build it directly:

pnpm --filter @heartidentity/heartify build

Usage

HEARTIFY_TOKEN=hrty_… heartify deploy ./dist --project test

| Flag | Env | Default | |---|---|---| | --project, -p | — | (required) | | --token | HEARTIFY_TOKEN | (required) | | --url | HEARTIFY_URL | https://heartify.ch | | --branch | auto (CI/git) | — | | --commit-sha / --commit-message | auto (CI/git) | — | | --idempotency-key | auto (gh-<run> / sha-<sha>) | — | | --no-comment | — | comments on PRs by default |

Branch and commit metadata are auto-detected from GitHub Actions env vars (falling back to local git). Control files _headers, _redirects, and _routes.json at the deploy root are passed through to Pages.

GitHub Actions

On a pull_request run the CLI also writes step outputs (view_url, index, deploy_id), a job summary, and upserts a PR comment with the preview URL (one comment per project, updated on each push). The PR comment needs pull-requests: write and GITHUB_TOKEN.

# .github/workflows/preview.yml
name: heartify preview
on:
  pull_request:

permissions:
  contents: read
  pull-requests: write   # for the preview comment

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: pnpm/action-setup@v4
      - uses: actions/setup-node@v4
        with: { node-version: '22', cache: pnpm }

      - run: pnpm install --frozen-lockfile

      - name: Build site
        run: pnpm build   # produces ./dist

      - name: Deploy preview to heartify
        env:
          HEARTIFY_TOKEN: ${{ secrets.HEARTIFY_TOKEN }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: npx @heartidentity/heartify deploy ./dist --project test

Token

Create a deploy token in the project's admin page → CI tokensCreate token (hrty_…, shown once). Store it as a GitHub Actions secret HEARTIFY_TOKEN. The token is scoped to that one project.