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

lockparse

v0.5.0

Published

A lightweight lockfile parser.

Readme

🔒 lockparse

A tiny zero-dependency lockfile parser for npm, Yarn, pnpm, and Bun.

⚠️ IMPORTANT: This library is in early development and the API may change without warning.

Installation

npm install lockparse

Usage

import { parse } from 'lockparse';
import { readFile } from 'node:fs/promises';

const lockfileContent = await readFile('./package-lock.json', 'utf-8');
const packageJson = JSON.parse(await readFile('./package.json', 'utf-8'));
const lockfile = parse(lockfileContent, 'npm', packageJson);

console.log(lockfile.root);

API

parse(input, typeOrFileName, packageJson?)

Parses a lockfile and returns a structured representation of the dependency tree.

Parameters

  • input (string): The lockfile content as a string
  • typeOrFileName (string): The lockfile type or filename. Supported values:
    • 'npm' or 'package-lock.json' - npm lockfile
    • 'yarn' or 'yarn.lock' - Yarn lockfile
    • 'pnpm' or 'pnpm-lock.yaml' - pnpm lockfile
    • 'bun' or 'bun.lock' - Bun lockfile
  • packageJson (PackageJsonLike, optional): The package.json object (optional but recommended for better accuracy)

Returns

Promise<ParsedLockFile> - A promise that resolves to an object with:

  • type (LockFileType): The detected lockfile type
  • packages (ParsedDependency[]): A flat array of all packages in the lockfile
  • root (ParsedDependency): The root dependency node representing the project dependency tree

Note: Yarn parsing

When parsing Yarn lockfiles, the packageJson parameter is highly recommended. Without it, the root node will not contain any dependencies as the Yarn lock file does not include this information. All packages will be in the packages array, though.

License

MIT