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

@forge-kit-dev/eslint-plugin-forge

v0.2.0

Published

Custom ESLint rules for forge modules (component-max-lines, no-boolean-flag-arg, fsd-slice-boundary, etc.).

Readme

@forge-kit-dev/eslint-plugin-forge

Custom ESLint rules that ship with forge modules. Anything that the existing ecosystem already covers well (@typescript-eslint/naming-convention, eslint-plugin-boundaries, eslint-plugin-react/boolean-prop-naming) stays outside this package — we only host rules forge needs that don't exist elsewhere.

Rules (v0.1 stubs)

| Rule | Module | Implemented in | |---|---|---| | forge/component-max-lines | module-clean-code | Step 3 | | forge/no-boolean-flag-arg | module-clean-code | Step 3 | | forge/fsd-slice-boundary | module-fsd | Step 2 | | forge/cqrs-layer-role | module-cqrs | Step 6 | | forge/ddd-entity-id | module-ddd | Step 4 | | forge/clean-arch-domain-isolation | module-clean-arch | Step 5 |

Every rule is registered and typechecked in v0.1; their bodies are empty until their owning module lands. This lets @forge-kit-dev/core and @forge-kit-dev/cli reference the rules from their default configs without breaking the workspace build.

Writing new rules

Use createRule from src/create-rule.ts so every rule gets a consistent docs URL pattern and plugs into the forge/* namespace.