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

@dannote/sloplint

v0.2.0

Published

AST-based multilingual AI slop linter — catches obvious comments, narrator comments, step comments, section dividers, empty catch blocks, and more across 8 languages

Readme

sloplint

AST-based multilingual linter that catches AI-generated code slop.

Powered by ast-grep via @ast-grep/napi — rules run on real syntax trees, not regex over text.

What it catches

Comment patterns (all 8 languages):

| Rule | Example | |------|---------| | obvious-comment | // Initialize the counter above let counter = 0 | | narrator-comment | // This function handles the request | | step-comment | // Step 1: Validate input | | section-divider | // ============ or // --- Helpers --- | | placeholder-comment | // ... rest of the code or // omitted for brevity | | apologetic-comment | // quick hack or // good enough for now | | ai-generated-comment | // Replace this with your actual implementation |

Code patterns (language-specific):

| Rule | Language | Example | |------|----------|---------| | empty-error-handler | TS/JS/Java/Python/Ruby | catch (e) {}, bare except:, empty rescue | | silent-exception | Python | except Exception: pass | | log-in-error-handler | TS/JS | console.log inside catch |

Supported languages

TypeScript, JavaScript, Python, Go, Rust, C, C++, Java, Ruby

Usage

# scan a directory
npx @dannote/sloplint src/

# scan specific files
npx @dannote/sloplint main.ts utils.py server.go

# scan everything
npx @dannote/sloplint .

Exits with code 1 if any problems are found.

What it ignores

Comments that provide actual value are never flagged:

  • // Wire format: 4-byte LE header followed by varint-encoded payload
  • // SAFETY: pointer is guaranteed valid by the borrow checker invariant above
  • // Mutex ordering: always acquire lockA before lockB to prevent deadlocks
  • // TODO: optimize later

Tool directives are also skipped: eslint-disable, noqa, nolint, NOLINT, clippy::allow, @ts-ignore, etc.

Install

npm install -D @dannote/sloplint

Philosophy

From the PR that inspired this:

Explicit anti-slop editing pass. Removed comments that restate what code does, dead code, unused includes, near-duplicate functions. Comments that remain document wire format specs, non-obvious constraints, or algorithm provenance.

Good comments explain why. Slop comments explain what — and the code already does that.