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

legion-toolkit

v0.5.0

Published

One install for the whole Legion toolkit: the lint plugin, the audit CLI, the Prettier config and the TypeScript configs, each exposed as a subpath.

Readme

legion-toolkit

One install for the whole toolkit behind LEGION-STANDARDS. Every tool is exposed as a subpath, so a repo never has to know the individual package names, and every tool added to the toolkit shows up here.

yarn add -D legion-toolkit oxlint prettier typescript

Installing runs nothing. A tool is on only where you reference it.

Lint (oxlint)

// .oxlintrc.json
{
  "jsPlugins": ["legion-toolkit/eslint-plugin"],
  "rules": { "legion/no-narrative-comments": "error" },
}

Or generate a full preset:

import { writeFileSync } from 'node:fs';
import { strict } from 'legion-toolkit/rules';

writeFileSync('.oxlintrc.json', JSON.stringify(strict.oxlint, null, 2));

Lint (ESLint)

import legion from 'legion-toolkit/eslint-plugin';

export default [...legion.configs.strict];

Prettier and TypeScript

// package.json
{ "prettier": "legion-toolkit/prettier" }
// tsconfig.json
{ "extends": "legion-toolkit/tsconfig/next.json" }

base.json, node.json, next.json, and react-native.json are available.

Audit

yarn legion-audit --md AUDIT.md --json audit.json
yarn legion-audit directives

The legion-audit command is provided by this package directly, so it works under Yarn, npm, and pnpm without relying on transitive bin linking.

Packages inside

| Subpath | Package | | ------------------------------ | ------------------------ | | legion-toolkit/eslint-plugin | eslint-plugin-legion | | legion-toolkit/rules | legion-rules | | legion-toolkit/audit | legion-audit | | legion-toolkit/prettier | legion-prettier-config | | legion-toolkit/tsconfig/* | legion-tsconfig |

Each is also published on its own for repos that want a smaller footprint.

Node 22 or newer. Peers (all optional): oxlint >= 1.53, eslint >= 9, prettier >= 3.

MIT, Copyright (c) 2026 Veracium LLC.