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

@defra/lis-infra-eslint-config

v0.6.0

Published

Shared ESLint flat config for the LIS ecosystem

Readme

lis-infra-eslint-config

Shared ESLint flat config for JavaScript/Node.js repos in the LIS ecosystem.

Using Defra's preferred neostandard as a base, this config adds sonarjs rules based on those enforced by the Defra JavaScript Standard from SonarQube. It also adds requirements for jsdoc, focussed on exported interfaces, to improve maintainability as well as to provide better experience for developers using IDEs and AI coding agents.

Stack: ESM · ESLint flat config (neostandard + sonarjs + jsdoc)


Usage

Install:

npm install --save-dev @defra/lis-infra-eslint-config

In your repo's eslint.config.js:

import lisEslintConfig from '@defra/lis-infra-eslint-config'

export default [
  ...lisEslintConfig
  // repo-specific overrides go here
]

Running locally

npm install
npm run lint       # eslint (lints this repo's own source using its own config)

Project structure

src/
├── index.js         # the exported ESLint flat config array
├── sonarjs.js        # sonarjs-derived rules, sourced from the Defra JS Sonar profile
└── jsdoc.js           # jsdoc rules, requiring docs on exported functions/methods

Patterns

  • Config changes here affect every consuming repo — treat this as a shared contract and version deliberately.
  • These files are flat config data, not logic, so they aren't unit tested — correctness is checked by this repo's own npm run lint dogfooding the config.