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

updates

v17.0.7

Published

Flexible dependency update tool

Downloads

47,866

Readme

updates

updates is a CLI tool which checks for dependency updates. It is typically able to complete in less than a second.

Supported files

  • package.json: supports all npm package managers
  • pyproject.toml: supports formats of uv and poetry
  • go.mod: experimental go support, will not be discovered go.mod in directory mode

Usage

# check for updates
npx updates

# update package.json and install new dependencies with your favorite package manager
npx updates -u && npm i

Options

See --help. Options that take multiple arguments can take them either via comma-separated value or by specifying the option multiple times. If an option has a optional pkg argument but none is given, the option will be applied to all packages instead.

All pkg options support glob matching via * or regex (on CLI, wrap the regex in slashes, e.g. '/^foo/').

Config File

The config file is used to configure certain options of the module. It is placed at updates.config.{js,ts,mjs,mts} or .config/updates.config.{js,ts,mjs,mts}, relative to package.json / pyproject.toml / go.mod.

Since Node.js v22.18.0, typescript configuration files work out of the box. For older node versions, set NODE_OPTIONS="--experimental-strip-types" in your environment.

import type {Config} from "updates";

export default {
  exclude: [
    "semver",
    "@vitejs/*",
    /^react(-dom)?$/,
  ],
} satisfies Config;

Config Options

  • include Array<string | RegExp>: Array of packages to include
  • exclude Array<string | RegExp>: Array of packages to exclude
  • types Array<string>: Array of package types to use
  • registry string: URL to npm registry
  • minAge number: Minimum package age in hours

CLI arguments have precedence over options in the config file. include and exclude options are merged.

© silverwind, distributed under BSD licence