npm4-check-updates

v2.11.5

Find newer versions of dependencies than what your package.json or bower.json allows For more information about how to use this package see README

Latest version published 5 years ago
License: Apache-2.0

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

60 / 100

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
2.11.5 | 06/2017
Popular
  • 0
    H
  • 0
    M
  • 0
    L
2.10.4 | 03/2017
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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

Small

Weekly Downloads (4)

Download trend
Dependents
0
GitHub Stars
7.73K
Forks
312
Contributors
110

Direct Usage Popularity


The npm package npm4-check-updates receives a total of 4 downloads a week. As such, we scored npm4-check-updates popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package npm4-check-updates, we found that it has been starred 7,728 times, and that 0 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

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
110
Funding
No

A good and healthy external contribution signal for npm4-check-updates project, which invites more than one hundred open source maintainers to collaborate on the repository.

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


Embed Package Health Score Badge

package health: 60/100 package health 60/100

Maintenance

Inactive

Commit Frequency

Open Issues
38
Open PR
2
Last Release
5 years ago
Last Commit
7 days ago

Further analysis of the maintenance status of npm4-check-updates 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 npm4-check-updates 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
>=0.12

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

npm4-check-updates 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.