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

@proappstore/compliance

v0.2.17

Published

Compliance checks for apps published on proappstore.online — used by the CLI for local feedback and by CI for gating.

Readme

@proappstore/compliance

Compliance checks for apps published on proappstore.online. Same checks the CLI runs locally and the template's CI runs on every push.

import { runChecks } from '@proappstore/compliance';

const results = await runChecks(process.cwd());
for (const r of results) {
  console.log(`${r.status}  ${r.name}  ${r.detail}`);
  for (const s of r.suggestions ?? []) console.log(`   → ${s}`);
}

Check ids and standard citations

Every result is decorated with a stable checkId, citations[] into the public Application Standard ({ clauseId, url }), an automation level (full | partial) and evidence ({ class, detail }). The mapping lives in src/clause-map.ts and is published at https://docs.proappstore.online/standard/compliance-checks.json; CHECKS, clauseUrl(), annotateByName() and complianceMap() are exported. Ids are never renamed. These checks are hygiene scans, not a security audit — see automation levels.

What is scanned

fsFileSource(dir) walks the working directory honouring every .gitignore it meets (nested files, ! re-includes, last match wins) and, regardless of .gitignore, skips .git, node_modules, dist, .next, .cache, .wrangler, .turbo and the generated-report directories .vibe-check, playwright-report, test-results, coverage, .vite, graphify-out. mapFileSource(map) — the publish gate, fed with the files that are actually in the repository — applies only the directory skip list: ignore rules never governed tracked files, so honouring them there could only hide real source. There is no separate ignore configuration; .gitignore is it.

Checks

runChecks(dir) (and runChecksFromFiles(map)) runs the full suite below. There is also a separate live-URL audit (auditLive, exported from @proappstore/compliance — a subset re-run against the deployed app).

| Name | What it checks | Status on fail | |---|---|---| | MIT License | A LICENSE file exists and is the MIT license | fail | | No .env.production | No committed .env.production | fail | | No template placeholders | No file still contains APPNAME | fail | | No tracking SDKs | No reference to any of the known trackers (google-analytics, gtag, amplitude, mixpanel, segment, hotjar, plausible, posthog) — hardened word-boundary matching via the shared TRACKERS / matchedTrackers | fail | | Brand fonts present | Manrope + Fraunces referenced in CSS or HTML | fail | | Brand tokens defined | Canonical brand CSS custom properties (--paper, --ink, --accent, …) are defined in theme CSS | fail | | No brand overrides | App does not redefine the platform-defined brand tokens/fonts | fail | | No scroll (games only) | Games fit the viewport — no document-level scroll (games only; skipped for non-games) | fail / warn | | Viewport support | Declares supported screens + orientations for the storefront coverage badge | fail / warn | | No unsafe 100vh | No bare 100vh (breaks on iOS Safari with the URL bar visible) | warn | | Accessibility static | Source-level baseline: image alt text, accessible button names, form control labels | fail | | HTML meta tags | web/index.html declares lang + viewport + non-empty title + share-preview images | fail | | PWA meta tags | web/index.html has an iOS/Android standalone install hint | fail / warn | | PWA offline correctness | Service worker / offline behaviour is correct | fail / warn | | PWA manifest | Static web/public/manifest.json (or inline VitePWA manifest) declares name / short_name / start_url / display | fail | | PWA maskable icon | Manifest declares at least one purpose: "maskable" icon | fail | | Dark mode support | Respects the system colour-scheme preference | warn | | Bundle size | Largest JS in web/dist/assets/ is ≤ 300 KB gzipped | fail if too big; warn if not built yet | | CLAUDE.md slim | Per-repo CLAUDE.md stays slim (no drift-prone platform-wide content) | warn |

License

MIT.