dependency-check

v4.1.0

checks which modules you have used in your code and then makes sure they are listed as dependencies in your package.json For more information about how to use this package see README

Latest version published 5 years ago

License: BSD-3-Clause

NPM

GitHub

Package Health Score

50 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
4.1.0	\|	07/2019	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.0.1	\|	07/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.4.1	\|	07/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.10.1	\|	03/2018		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.9.2	\|	12/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

BSD-3-Clause

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (42,707)

GitHub Stars: 546
Forks: 38
Contributors: -

Direct Usage Popularity

The npm package dependency-check receives a total of 42,707 downloads a week. As such, we scored dependency-check popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package dependency-check, we found that it has been starred 546 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 0
Funding: Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like dependency-check is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 5 years ago
Last Commit: 10 months ago

Further analysis of the maintenance status of dependency-check based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for dependency-check is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=10.0.0

Age: 11 years
Dependencies: 9 Direct
Versions: 52
Install Size: 23.1 kB
Dist-tags: 3
# of Files: 6
Maintainers: 3
TS Typings: No

dependency-check has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

dependency-check

checks which modules you have used in your code and then makes sure they are listed as dependencies in your package.json, or vice-versa

requirements for maintained majors

If used on an older Node.js version dependency-check will fail silently rather than crashing your tests.

5.x supports Node.js 14 and later
4.x supports Node.js 10 and later
3.x supports Node.js 6 and later
2.x supports Node.js 0.10 and later (Dev note: published using the legacy tag)

For more info on maintenance status, see SECURITY.md.

how it works

dependency-check parses your module code starting from the default entry files (e.g. index.js or main and any bin commands defined in package.json or if specific files has been defined, then those) and traverses through all relatively required JS files, ultimately producing a list of non-relative modules

relative - e.g. require('./a-relative-file.js'), if one of these are encountered the required file will be recursively parsed by the dependency-check algorithm
non-relative - e.g. require('a-module'), if one of these are encountered it will get added to the list of dependencies, but sub-dependencies of the module will not get recursively parsed

the goal of this module is to simply check that all non-relative modules that get require()'d are in package.json, which prevents people from getting 'module not found' errors when they install your module that has missing deps which was accidentally published to NPM (happened to me all the time, hence the impetus to write this module).

cli usage

$ npm install dependency-check -g
$ dependency-check

dependency-check dependencies

debug detective globby is-relative micromatch minimist pkg-up read-package-json resolve

dependency-check development dependencies

detective-cjs husky installed-check npm-run-all standard

FAQs

What is dependency-check?

checks which modules you have used in your code and then makes sure they are listed as dependencies in your package.jso... Visit Snyk Advisor to see a full health score report for dependency-check, including popularity, security, maintenance & community analysis.

Is dependency-check popular?

The npm package dependency-check receives a total of 42,707 weekly downloads. As such, dependency-check popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is dependency-check well maintained?

We found indications that dependency-check is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is dependency-check safe to use?

The npm package dependency-check was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 19 December-2024, at 08:46 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (42,707)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

dependency-check

requirements for maintained majors

how it works

cli usage

dependency-check dependencies

dependency-check development dependencies

FAQs

What is dependency-check?

Is dependency-check popular?

Is dependency-check well maintained?

Is dependency-check safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues