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

@clistd/clig-rules

v0.0.0

Published

Command Line Interface Guidelines lint rules for clistd documents.

Downloads

47

Readme

@clistd/clig-rules

Portable rules derived from the Command Line Interface Guidelines. They apply only guidance that can be evaluated from a canonical clistd document.

npm install @clistd/clig-rules
import { cligRules } from '@clistd/clig-rules';
import { createRuleRegistry, runRules } from '@clistd/linter';

const diagnostics = runRules(ast, createRuleRegistry(cligRules));

Individual rules are exported alongside the ordered cligRules collection.

Included rules

| Rule | Default | Purpose | | -------------------------------- | ------- | ----------------------------------------------------------------- | | clig/command-name-style | warn | CLI names use lowercase letters and dashes. | | clig/standard-flag-names | warn | Conventional flags use conventional short forms. | | clig/prefer-flags-to-arguments | warn | Multiple distinct required positionals should generally be flags. | | clig/no-secret-value-flag | warn | Secrets should not be accepted as flag values. | | clig/require-json-output-flag | off | Declared JSON output should be selectable with --json. | | clig/require-success-exit-code | off | Commands should document exit code 0. | | clig/require-failure-exit-code | off | Commands should document a non-zero failure exit code. |

Enable optional runtime-contract documentation checks explicitly:

rules:
  clig/require-success-exit-code: warn
  clig/require-failure-exit-code: warn

For the baseline documentation-quality rules, use @clistd/recommend-rules.