alert

mversion

v2.0.1

A cross packaging manager module version handler/bumper

MIT
Latest version published 12 months ago
    npm install mversion
  

Package Health Score

58 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Small
Download trend

Weekly Downloads (4,045)

Dependents
368
GitHub Stars
200
Forks
20
Contributors
20

The npm package mversion receives a total of 4,045 downloads a week. As such, we scored mversion popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package mversion, we found that it has been starred 200 times, and that 368 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

02/2014
04/2014
07/2014
02/2019
06/2020

Direct Vulnerabilities

0.3.1
0.4.3
0.5.1
Popular
1.13.0
2.0.1
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.3.1
Popular
1.13.0
2.0.1

License Risk

0.3.1
  • 0
    H
  • 0
    M
  • 0
    L
0.4.3
  • 0
    H
  • 0
    M
  • 0
    L
0.5.1
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.13.0
  • 0
    H
  • 0
    M
  • 0
    L
2.0.1
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like mversion is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test mversion
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

Open Issues
12
Open PR
6
Last Release
12 months ago
Last Commit
12 months ago

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

We found that mversion 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.

Community

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

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


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
10 Direct
Versions
36
Install Size
27.6 kB
Dist-tags
1
# of Files
10
Maintainers
1
TS Typings
No

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