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

brewlint

v0.1.1

Published

Static analysis for Spring Boot anti-patterns. Curated rules with a Java parser, not regex.

Readme

brewlint

Static analysis for Spring Boot anti-patterns. Curated rules with a Java parser, not regex.

The bugs it looks for share a shape: the code looks right, compiles, deploys, and then quietly does nothing. @Transactional on a private method is accepted by the compiler, accepted by the container, and never opens a transaction.

Install

npm install -g brewlint

No Java required. The package carries a self-contained runtime, so it works on a machine that has never had a JDK installed.

| Platform | Binary | |---|---| | macOS on Apple Silicon | brewlint-macos-arm64 | | Linux on x86-64 | brewlint-linux-x64 | | Windows on x86-64 | brewlint-win-x64 |

Those are optional dependencies: npm installs the one that matches your platform and skips the rest. You never install them by hand.

Use

brewlint scan
brewlint scan --path src/main/java
brewlint scan --format json --output report.json
brewlint scan --list-rules

| Option | Meaning | |---|---| | -p, --path <dir> | Directory or single .java file. Default: current directory | | --format <format> | terminal or json. Default: terminal | | -o, --output <file> | Write to a file instead of standard output | | --fail-on <severity> | Exit 1 at or above ERROR, WARNING, INFO or NONE | | --no-color / --color | Force ANSI escapes off or on |

Exit codes: 0 clean, 1 findings over the threshold, 2 could not run.

Rules

AOP001 proxy-dependent annotation on a non-proxyable method · TX002 self-invoked transaction · TX003 missing rollbackFor on a checked exception · RES001 unclosed stream or JDBC resource · RES002 unclosed Files stream · BEAN001 entity also annotated as a bean · BEAN002 prototype bean in a singleton · BEAN003 field injection

Configure

A brewlint.yml in the project root. Every key is optional.

rules:
  AOP001: true
  RES001:
    enabled: true
    severity: WARNING
exclude:
  - "**/generated/**"

Programmatic use

const { binaryPath } = require('brewlint');

Returns the absolute path to the binary, for tools that spawn it as a subprocess. This is the entry point the VS Code extension uses.

Links