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

@hatchingpoint/point-logic

v0.0.3

Published

App store listing readiness logic authored in Point and published as emitted JavaScript.

Downloads

284

Readme

@hatchingpoint/point-logic

Store listing readiness scoring logic for app publishers. Source of truth is Point (src/*.point only) — there is no hand-written TypeScript in src/. The published API is emitted JavaScript in dist/.

Install

npm install @hatchingpoint/point-logic
# or
bun add @hatchingpoint/point-logic

Requires a runtime that supports ES modules (Node 18+, Bun, or bundlers that resolve import).

Use

import { listingScore, listingStatusLabel } from "@hatchingpoint/point-logic";

const signals = {
  hasScreenshots: true,
  hasDescription: true,
  hasPrivacyPolicy: true,
  hasSupportUrl: true,
  hasAgeRating: true,
};

const score = listingScore(signals); // 100
const status = listingStatusLabel(score); // "Ready to submit"

Field names

Emitted JavaScript uses camelCase record fields (hasScreenshots, hasDescription, etc.) matching Point’s naming rules.

Build from source (monorepo)

From the Point repo root:

bun run --cwd packages/point-logic check
bun run --cwd packages/point-logic build

build runs point build on src/store-readiness.point and writes dist/store-readiness.js. Run prepublishOnly automatically before npm publish.

Package layout

| Path | Role | |------|------| | src/store-readiness.point | Authoritative semantic Point module | | point.json | Point project manifest | | dist/store-readiness.js | Generated JS (npm files — not edited by hand) |

Do not add .ts files under src/. Extend behavior by editing .point and rebuilding.