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

ditched

v6.1.1

Published

List dependencies that haven't been updated in a long time.

Readme

ditched

Command line tool to find npm dependencies that have been ditched. A ditched package is one that has not been updated in more than one year.

This is a fork of the abandoned project abandoned.

The output lists the age (in days) and name of all ditched packages:

> npx ditched
1619  cli-table
919   @types/cli-table

If there are no ditched packages, there will be no output.

How to Use

Within your project, run

npx ditched

You can also install it as a dev dependency and use it in your scripts, for example as part of your build procedure or as a reminder after install.

npm install --dev ditched

package.json:

"scripts": {
  "test": "ditched",
  "postinstall": "ditched"
}

Reference

ditched [files..]

List dependencies that haven't been updated in a long time.

Positionals:
  files  One or more package.json files to check (default "./package.json").
         Pass "-" to read newline-delimited paths from stdin.           [string]

Options:
      --help         Show help                                         [boolean]
      --version      Show version number                               [boolean]
  -d, --days         The number of days since last release needed to consider a
                     package as ditched                  [number] [default: 365]
  -c, --concurrency  The maximum number of concurrent registry requests (one
                     request per package)                 [number] [default: 20]
  -r, --registry     The URL of the npm registry to use
                                [string] [default: "https://registry.npmjs.org"]
  -i, --include      Which dependency types to include when reading
                     package.json. Use -i multiple times or provide a
                     whitespace-separated list to include multiple types.
        [array] [choices: "dependencies", "devDependencies", "peerDependencies",
           "optionalDependencies"] [default: ["dependencies","devDependencies"]]

Examples:
  ditched --days 14                         Find packages in the current
                                            directory's package.json with no
                                            releases in the last 14 days.
  ditched --include dependencies            Include all dependency types when
  devDependencies peerDependencies          checking for ditched packages (not
  optionalDependencies                      just dependencies and
                                            devDependencies).
  ditched ./package.json                    Monorepo: Find ditched packages in
  ./packages/*/package.json                 the specified package.json files.
  ditched -i dependencies --                Only check production dependencies
  ./package.json ./packages/*/package.json  in a monorepo. Use the -- separator
                                            to avoid ambiguity between the -i
                                            flag and positional file arguments.
  find . -name package.json | ditched -     Read newline-delimited package.json
                                            paths from stdin.

Examples

Sort by age, descending:

ditched | sort -rn

Get age of all dependencies by setting age limit to 0:

ditched --days 0

Fail fast on first found ditched dependency:

set -o pipefail; ditched | head -1

Find ditched dependencies in a monorepo using explicit paths:

ditched package.json packages/**/package.json

Or recursively find all package.json files excluding those inside node_modules:

find . -name "node_modules" -prune -o -type f -name "package.json" -print | ditched -

Check transitive dependencies multiple levels deep with npm list:

npm list -p --depth=3 | sed 's/$/\/package.json/' | ditched -