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

cyf-lint

v0.1.6

Published

A simple tool to quickly [lint](<https://en.wikipedia.org/wiki/Lint_(software)>) your JavaScript code.

Readme

CYF Lint

A simple tool to quickly lint your JavaScript code.

Its main goal is to highlight those practices that, while technically correct, are generally discouraged:

  • Potential syntax and logic errors
  • Sloppy and unconventional coding style

Usage

$ npx cyf-lint [--fix] <path> [<path> ...]

You can find the details of any failing rule at https://eslint.org/docs/rules/

--fix fixes some of the failing rules automatically. While safe, it's a good idea to use it on a repo without uncommitted changes.

Example

$ cd my-project
$ npx cyf-lint .

FAQ

  • How can I automatically run it every time I make a change in the code?

    $ npx onchange -i '**/*.js' -- npx cyf-lint .
  • It takes a long time to run!

    That's probably npx (re)installing cyf-lint every time it's executed. The only way to speed it up that I'm aware of is to manually install cyf-lint:

    $ npm install -g cyf-lint

    Note in this case you won't be using the latest version automatically. To ensure you are up to date, remember to update the package periodically:

    $ npm install -g cyf-lint@latest
  • I get warnings on a piece of code I consider legitimate. What can I do?

    It may very well be a bug or that the rules are unfairly restrictive. In that case, please file an issue.

    If it's more of an edge case and you would like to ignore that case especifically, you can do that by commenting your code.

Development

To apply the rules to the project itself:

$ npm run dev

To apply the rules to other projects:

$ cd sample-project
$ npx onchange -i '**/*.js' '<cyf-lint-dir>/**' -- <cyf-lint-dir>/bin/cyf-lint .

TODO

  • tsc + checkJs
  • Errors to link to the rules
  • Integrated watch mode
  • Expose ESLint config