mv

v2.1.1

fs.rename but works across devices. same as the unix utility 'mv'

MIT
Latest version published 6 years ago
    npm install mv
  

Package Health Score

67 / 100

Popularity

Influential project

Weekly Downloads (1,520,257)

Download trend
Dependents
594
GitHub Stars
150
Forks
21
Contributors
4

Direct Usage Popularity

TOP 5%

The npm package mv receives a total of 1,520,257 downloads a week. As such, we scored mv popularity level to be Influential project.

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

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

03/2013
09/2013
07/2014
06/2015

Direct Vulnerabilities

0.0.5
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.1.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.5
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.1.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.0.5
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
2.0.3
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.1.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 mv 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 mv
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
12
Open PR
5
Last Release
6 years ago
Last Commit
6 years ago

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

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 67/100 package health 67/100

Package

Node.js Compatibility
>=0.8.0

Age
9 years
Dependencies
3 Direct
Versions
13
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

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