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

@jpeakai/prose-gates

v0.1.2

Published

Deterministic prose gates for markdown documentation

Vulnerabilities

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

Links

Git

Maintainers

neozenithneozenith

Keywords

markdownproselintdocumentation

Readme

jpai-prose-gates

Reading markdown should not be hard. Keep AI accountable one anti-slop rule at a time.

Rules | GitHub | npm

| Package Index | Published Version | Downloads | Node | CI | License | |---|---|---|---|---|---| | npm | npm | npm Downloads | Node | CI | License |

Usage

bunx @jpeakai/prose-gates README.md docs/*.md     # report findings, exit 1 if any
npx -y @jpeakai/prose-gates --fix README.md  # apply every fix proven safe, report the rest

Installed as a dev dependency, the command is prose-gates, and --json gives machine-readable output.

--max-words N changes the sentence budget, which defaults to 25. Exit codes are 0 for clean, 1 for findings, and 2 for a usage error.

The rules

Nine rules in three categories. RULES.md shows a failing example and the fix for each one. docs/DATA_MODEL.md diagrams how a rule is checked, fixed and verified.

| Category | Rules | What it guards | |---|---|---| | Sentence | PG001, PG002 | How a sentence is laid out and how long it runs | | List | PG003, PG006, PG007, PG008, PG009 | A list hidden in running prose, promoted to a real markdown list | | Punctuation | PG004, PG005 | A glyph that reads as generated text |

Every fix is verified before it is written. A fix that would change a word, url or code value is a bug and fails the run. A case the fixer cannot read unambiguously is refused, so the finding stays for a human. The reasoning behind each choice is recorded in adrs/.

Code blocks are exempt. Fences tagged markdown or md are the exception, since they hold templates whose body is audited recursively.

Consuming it

Each meta repo declares this package and runs it through a docs-ci target.

bun add --dev @jpeakai/prose-gates

npm works the same way, with npm install --save-dev @jpeakai/prose-gates. The library exports checkMarkdown and fixMarkdown. Bun imports the TypeScript source, and Node imports the bundle in dist/.

Generated markdown is gated too. A finding there is traced back to the source that rendered it, either the record or the template, and never fixed in the output.

Development

See CONTRIBUTING.md for setup, the make targets and how a change is accepted. Releases are covered in docs/PUBLISHING.md.

License

MIT, see LICENSE.