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

@logeix/prose-check

v1.0.2

Published

Readability and AI-tell audit for local business web copy. Zero dependencies.

Readme

@logeix/prose-check

Readability and AI-tell audit for local business web copy. Zero dependencies.

npm i -g @logeix/prose-check
prose-check "dist/*-plumbers" --show 5

Reads built HTML (visible <main> copy, chrome stripped) or Markdown.

| Metric | Why | | --- | --- | | Reading grade | Service copy should sit at 6–8; longer sentences, not vocabulary, are the usual cause of drift | | Mean / long sentence % | One idea per sentence | | Burstiness | Uniform sentence length reads as machine-written | | Em dash per 1k | Human range is roughly 4–10; flagged well above that, not banned | | Triplets per 200 words | Three-item lists with matched rhythm are a strong tell | | Contrast frames | "not just X, it's Y" and friends | | Unique % across files | Google treats near-identical city pages as doorway pages |

Duplication is compared within a content type, so a blog post is never measured against a landing page.

Shingles appearing on every page in a set are treated as shared components — service cards, trust strips, CTA banners — and subtracted before the comparison. Counting them makes any component-driven site look templated when it is not. uniquePct describes the page-specific copy a writer controls; chromePct reports how much of each page is furniture.

Options

--type <page|blog|gbp|meta>  threshold profile (default: inferred from path)
--strict                     exit 1 when a threshold is breached
--show <n>                   list n worst sentences per file, with reasons
--no-dup                     skip cross-file duplication
--json                       machine-readable output

Profiles

| Type | Grade | Avg sentence | Unique | | --- | --- | --- | --- | | page | ≤7.5 | ≤17 | ≥60% | | blog | ≤8.5 | ≤20 | — | | gbp | ≤6.5 | ≤15 | — | | meta | ≤8 | ≤18 | — |

Pages under 120 words, and link lists or paginated indexes where sentence splitting is meaningless, are skipped rather than scored.