1. Advisor
  2. JavaScript packages
  3. update-versions

update-versions

v7.0.4

Like npm-check-updates but supports Lerna monorepos and enforces strict semver values For more information about how to use this package see README

Latest version published 7 months ago
License: MIT
NPM
GitHub

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

50 / 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
7.0.4 | 06/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.19 | 12/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.2.12 | 11/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.1.0 | 05/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.5.8 | 07/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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

Limited

Weekly Downloads (185)

Download trend
GitHub Stars
190
Forks
26
Contributors
3

Direct Usage Popularity

Uncommon

The npm package update-versions receives a total of 185 downloads a week. As such, we scored update-versions popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package update-versions, we found that it has been starred 190 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
3
Funding
No

This project has seen only 10 or less contributors.

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

Embed Package Health Score Badge

package health: 50/100 package health 50/100

Maintenance

Inactive

Commit Frequency

Open Issues
13
Open PR
0
Last Release
7 months ago
Last Commit
2 months ago

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

We found that update-versions demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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

scan-reversed

Check your package.json

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

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
>=18
Age
6 years
Dependencies
14 Direct
Versions
161
Install Size
25.9 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
No

update-versions 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.