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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@rnx-kit/lint-lockfile

v0.1.1

Published

Tool for linting lockfiles

Readme

@rnx-kit/lint-lockfile

Build npm version

🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧

THIS TOOL IS EXPERIMENTAL — USE WITH CAUTION

🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧

@rnx-kit/lint-lockfile is a standalone tool for scanning your lockfiles for potential issues.

Supported lockfile formats:

Installation

yarn add @rnx-kit/lint-lockfile --dev

Usage

yarn lint-lockfile

Configuration

@rnx-kit/lint-lockfile can be configured in your root package.json file. For example:

{
  "rnx-kit": {
    "lint": {
      "lockfile": {
        "noDuplicates": {
          "enabled": true, // enabled by default
          "packages": [
            "react",
            "react-native"
          ]
        },
        "noWorkspacePackageFromNpm": {
          "enabled": true // enabled by default
        }
      }
    }
  }
}

Rules

noDuplicates

This rule checks for duplicate packages in the lockfile. It must be configured to check for specific packages. For example, to check for duplicates of React and React Native, configure it like this:

{
  "rnx-kit": {
    "lint": {
      "lockfile": {
        "noDuplicates": {
          "packages": [
            "react",
            "react-native"
          ]
        }
      }
    }
  }
}

You can allow multiple copies of a package by specifying a max count:

{
  "rnx-kit": {
    "lint": {
      "lockfile": {
        "noDuplicates": {
          "packages": [
            "react-native",
            ["react", 2], // allow up to 2 copies of `react`
            ["left-pad", 0] // disallow `left-pad` entirely
          ]
        }
      }
    }
  }
}

This rule also has a built-in preset for React Native. You can enable it with #react-native:

{
  "rnx-kit": {
    "lint": {
      "lockfile": {
        "noDuplicates": {
          "packages": [
            "#react-native"
          ]
        }
      }
    }
  }
}

noWorkspacePackageFromNpm

This rule checks for workspace packages that are unintentionally installed from npm. It is enabled by default, but can be disabled like this:

{
  "rnx-kit": {
    "lint": {
      "lockfile": {
        "noWorkspacePackageFromNpm": {
          "enabled": false
        }
      }
    }
  }
}