compare-versions

v6.1.0

Compare semver version strings to find greater, equal or lesser. For more information about how to use this package see README

Latest version published 7 months 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

78 / 100

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
6.1.0 | 08/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.0 | 07/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.0.3 | 12/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.1.4 | 08/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.6.0 | 02/2020
Popular
  • 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

Influential project

Weekly Downloads (4,326,880)

Download trend
GitHub Stars
565
Forks
50
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package compare-versions receives a total of 4,326,880 downloads a week. As such, we scored compare-versions popularity level to be Influential project.

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

With more than 10 contributors for the compare-versions 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 compare-versions is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 78/100 package health 78/100

Maintenance

Sustainable

Commit Frequency

Open Issues
2
Open PR
1
Last Release
7 months ago
Last Commit
3 months ago

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

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

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
not defined

Age
9 years
Dependencies
0 Direct
Versions
37
Install Size
55.2 kB
Dist-tags
1
# of Files
29
Maintainers
1
TS Typings
Yes

compare-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.