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

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

45 / 100

Explore Similar Packages

Security

Security review needed
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
  • 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

Small

Weekly Downloads (8,722)

Download trend
GitHub Stars
545
Forks
38
Contributors
30

Direct Usage Popularity

TOP 5%

The npm package dependency-check receives a total of 8,722 downloads a week. As such, we scored dependency-check popularity level to be Small.

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

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

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
30
Funding
Yes

With more than 10 contributors for the dependency-check repository, this is possibly a sign for a growing and inviting community.

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

package health: 45/100 package health 45/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
0
Open PR
0
Last Release
5 years ago
Last Commit
8 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.

Package

Node.js Compatibility
>=10.0.0

Age
10 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.