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

eslint-disable-scanner

v1.1.0

Published

A tool to check for disabled ESLint rules in JavaScript/TypeScript projects.

Readme

eslint-disable-scanner

A lightweight tool to detect and report ESLint disabled rules in your JavaScript/TypeScript projects.

Overview

eslint-disable-scanner helps you maintain code quality by identifying where ESLint rules have been disabled in your codebase. It scans for eslint-disable comments and reports them in a clear, organized format, making it easier to track and review disabled rules.

Features

  • 🔍 Detects all forms of eslint-disable comments
  • 📊 Groups findings by file for better readability
  • ⚡ Fast and lightweight
  • 🔧 Works with your existing ESLint configuration
  • 🚀 Perfect for CI/CD pipelines

Installation

npm install eslint-disable-scanner --save-dev

Usage

Run in your project directory:

npx eslint-disable-scanner

Example output:

Running eslint-disable-checker...

✖ Found 2 error rules and 1 warning rule disabled:

src/main.ts
  1:1     error  Rule 'no-console' was disabled.
  10:29   warning  Rule '@typescript-eslint/no-floating-promises' was disabled.

src/app.service.ts
  6:33   error  Rule 'no-console' was disabled.

✖ Found disabled ESLint error rules. Process will stop.

Allowlist & Reasons

To handle legitimate cases where rules need to be disabled, create a .eslint-disable-allow.json in your project root:

{
  "allowedRules": ["@typescript-eslint/no-explicit-any"],
  "allowedPatterns": ["scripts/**"]
}

Any disabled rule that is not listed in allowedRules/allowedPatterns must have a -- reason at the end of the eslint-disable comment:

// eslint-disable-next-line @typescript-eslint/no-explicit-any -- parse dynamic JSON
  • Error rules without a reason will cause the process to fail.
  • Error rules with a reason or allowed rules/patterns will only produce a warning.
  • Warning rules will only produce warnings.

CI/CD Integration

Add to your CI pipeline to prevent unwanted rule disabling:

npx eslint-disable-scanner

The command will exit with code 1 if any disabled rules are found, making it perfect for CI/CD enforcement.

Contributing

Contributions are welcome! Feel free to:

  • Report bugs
  • Suggest features
  • Submit pull requests

License

MIT - see LICENSE for details.