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

disclosure

v0.1.0

Published

Project dependencies overview

Downloads

10

Readme

Disclosure

js-standard-style

demo

Motivation

The Node.js culture is very active in creating and publishing modules for almost every imaginable need. On average, a Node.js project has a lot more dependencies than in projects with other technologies like .NET or Java. Managing those dependencies can become be overwhelming if the project has hard requirements in terms of reliability or legal. There are too many modules to approve, vetting, monitor, etc. This tool will give you an an overview of a project's dependencies, so you know what you are exposed to regarding licenses, reliability and overall risk.

Installation

$ npm i disclosure -g

Usage

$ disclosure <path>

Options

--reporter <reporter>

The only available reporter at the moment is table. More reporters should follow.

table

$ disclosure --reporter table .

Can I build my own reporter?

Sure, disclosure by default outputs JSON. So you can pipe the stdout to your custom reporter.

$ disclosure . | my-prettify-module

--licenses [licenses]

$ disclosure . --licenses "MIT,ISC,Apache-2.0"

This option let you pass a custom license whitelist instead of using the default one.

Separate the licenses by comma and use only valid SPDX licenses ids.

--licenses-file [licensesFile]

$ disclosure . --licenses-file license.json

The same functionality as described before but instead uses a file content as the license white list.

Node.js API

disclosure(projectPath, [options], callback)

projectPath should be a valid absolute or relative path. An opts object may be provided:

var opts = {
  licenses: ['MIT', 'ISC'] // Licenses whitelist - Only valid SPDX licenses ids
}

The callback will be called with an Error and results object:

var results = {
  name: '...',
  version: '1.33.7',
  sloc: {
    real: 1234
    pkg: 100
  },
  tests: {
    exists: true,
    framework: true,
    npmScript: true
  },
  license: 'MIT',
  dependencies: {...},
  dependenciesCount: 13,
  isOutdated: false,
  isDeprecated: false,
  vulnerabilities: [...],
  private: false,
  __moduleData: {
    version: '1.0.0',
    type: 'standard'
  }
}

Disclosure core

The disclosure core is two modules that you should definitely check out and those are:

  • module-data - Traverse local module data and query remote module data.
  • module-rank - Our rank formula using the data acquired by module-data

Formula breakdown

We have three areas of concern and those are:

  • Security
  • Reliability
  • License

Each has a weight of 1, so each represent roughly 33% of the final score.

Security

The criteria of Security for public modules is:

  • noVuln - This is an array of objects that comes from snyk.

For private modules, there is no criteria to evaluate.

Reliability

The criteria of Reliability for public modules is:

  • hasTests
  • isNotOutdated
  • isNotDeprecated - If this is false, the score of this area of concern is 0.

For private modules is:

  • hasTests

License

The criteria of License for public and private modules is:

  • hasLicense
  • licenseOnWhiteList

Both need to have a score of 1 to have a positive score or else the final score of this area is 0.