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

@anthony-dius/clarity

v0.3.0

Published

Standalone ASD-STE100 CLI documentation checker

Readme

Clarity

A standalone CLI that checks documentation, specs, and agent-instruction files against ten writing rules derived from ASD-STE100 (the aerospace "Simplified Technical English" standard), targeting the verbose/hedging/vague prose patterns common in AI-generated text.

Install

Pick whichever path fits:

# No install — run once via npx
npx @anthony-dius/clarity path/to/doc.md

# Install globally via npm
npm install -g @anthony-dius/clarity
clarity path/to/doc.md

# Download a prebuilt binary (no Node/npm required at all)
# — pick the asset matching your platform from the release page:
# https://github.com/anthony-dius/clarity/releases/latest
curl -LO https://github.com/anthony-dius/clarity/releases/latest/download/clarity-linux-x64
chmod +x clarity-linux-x64
./clarity-linux-x64 path/to/doc.md

Verifying a release: every binary and the npm package are built by CI from a tagged commit, never uploaded by hand. Check a binary against the release's SHA256SUMS, or verify cryptographic build provenance directly:

gh attestation verify clarity-linux-x64 --repo anthony-dius/clarity

The npm package carries the equivalent provenance, shown as a "Provenance" badge on its npmjs.com page, linking back to the exact GitHub Actions run that published it.

Usage

clarity path/to/doc.md              # check one file
clarity a.md b.md c.md              # check multiple files
clarity --json path/to/doc.md       # machine-readable output
clarity --version                   # tool + rule-set version
clarity --help                      # usage + the 10 built-in rules

No config file, no flags required for the common case — clarity <file> is the whole interface. Exit code is 0 when every checked file passes with no findings, 1 when any finding is reported. Every finding names the file and location, the rule and ASD-STE100 principle it maps to, and a concrete remediation instruction.

Full CLI contract: specs/001-ste100-cli-checker/contracts/cli.md.

Contributing

See CONTRIBUTING.md. For dev environment setup (prerequisites, building from source, this repo's non-standard tooling), see docs/DEVELOPMENT.md.