check-dependencies

v1.1.0

Checks if currently installed npm/bower dependencies are installed in the exact same versions that are specified in package.json/bower.json For more information about how to use this package see README

Latest version published 5 years ago
License: MIT

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

47 / 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
1.1.0 | 08/2017
Popular
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 08/2016
  • 0
    H
  • 0
    M
  • 0
    L
0.12.3 | 08/2016
  • 0
    H
  • 0
    M
  • 0
    L
0.11.0 | 10/2015
  • 0
    H
  • 0
    M
  • 0
    L
0.10.3 | 09/2015
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

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 (99,388)

Download trend
Dependents
112
GitHub Stars
115
Forks
31
Contributors
9

Direct Usage Popularity

TOP 5%

The npm package check-dependencies receives a total of 99,388 downloads a week. As such, we scored check-dependencies popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package check-dependencies, we found that it has been starred 115 times, and that 112 other projects in the ecosystem are dependent on it.

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
9
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 47/100 package health 47/100

Maintenance

Inactive

Commit Frequency

Open Issues
15
Open PR
3
Last Release
5 years ago
Last Commit
10 months ago

Further analysis of the maintenance status of check-dependencies 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 check-dependencies 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=4.4 <6 || >=6.9

Age
9 years
Dependencies
6 Direct
Versions
41
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

check-dependencies 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.