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

@project-eleven/dep-doc

v0.0.4

Published

A Typescript library for linting dependency documentation.

Readme

Dep Doc

A TypeScript library for linting dependency documentation.

It currently supports linting dependency documentation, via a dep-doc.toml file for:

  • package.json projects (Node.js/JavaScript/TypeScript projects)
  • Cargo.toml projects (Rust projects)

Motivation.

Dep Doc requires that all dependencies in a project are listed in the dep-doc.toml file. This ensures that developers understand the purpose and usage of each dependency, leading to better maintainability and collaboration within teams.

It also makes the use of each dependency explicit, reducing the risk of unnecessary or outdated dependencies lingering in the codebase and helping to catch potential security vulnerabilities associated with unused or poorly understood dependencies.

How it works

Dep Doc scans the project's dependency list (e.g., from package.json/Cargo.toml) and checks for the presence of a dep-doc.toml file in the root directory. The dep-doc.toml file should explain why each dependency is included, its purpose, and any relevant usage information.

The current schema for dep-doc.toml is as follows:

  • name (string): The name of the dependency.
  • purpose (string): A brief description of why the dependency is included in the project.
  • scope (string, optional): The scope of the dependency (enums: "dev", "prod", "build").
[[dependency]]
name = "serde"
purpose = "Serializing stuff"
scope = "prod"

[[dependency]]
name = "leftpad"
purpose = "Utility function"
scope = "prod"

Linting will fail if:

  • Any dependency in the project is missing from dep-doc.toml.
  • Any dependency in dep-doc.toml is not present in the project.
  • Any dependency in dep-doc.toml does not adhere to the schema (e.g., missing purpose).
  • Any depedency is incorrectly scoped (e.g., a dev dependency marked as prod).

Usage

To use Dep Doc, install it via npm:

npm install -g @project-eleven/dep-doc

Then, you can run the linter using the command line:

dep-doc --run

It can be used locally & in CI.

To get the version of dep-doc you have installed, run:

dep-doc --version

Contributing

See CONTRIBUTING.md for details on how to contribute to this project.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Note on releasing:

Run ./setup.sh to install git hooks.

You must bump the version in package.jsonbefore creating a release.