Vulnerability Database · npm · Package report
mv: vulnerability history, versions and safety
mv is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on mv 2.1.1 i
Updated on 23 Oct 2026
Good news: 2.1.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Inactive
What to do: Stay on 2.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 12,899 packages i
- Stars 157 i
- OpenSSF scorecard 1/10 i
- Last release 136 months ago i
- Licence MIT i
- Similar names ms i
Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for mv, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- 2.1.1 22 Jun 2015
- 2.1.0 19 Jun 2015
- 2.0.3 26 Jul 2014
- 2.0.2 26 Jul 2014
- 2.0.1 30 Jun 2014
- 2.0.0 26 Feb 2014
- 1.0.0 08 Sep 2013
- 0.0.5 12 Mar 2013
- 0.0.4 12 Dec 2012
- 0.0.3 12 Oct 2012
- 0.0.2 12 Oct 2012
- 0.0.1 12 Oct 2012
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 2.1.1 | 22 Jun 2015 | none | MIT | — | Details → |
| 2.1.0 | 19 Jun 2015 | none | MIT | — | Details → |
| 2.0.3 | 26 Jul 2014 | none | MIT | — | Details → |
| 2.0.2 | 26 Jul 2014 | none | MIT | — | Details → |
| 2.0.1 | 30 Jun 2014 | none | non-standard | — | Details → |
| 2.0.0 | 26 Feb 2014 | none | non-standard | — | Details → |
| 1.0.0 | 08 Sep 2013 | none | non-standard | — | Details → |
| 0.0.5 | 12 Mar 2013 | none | non-standard | — | Details → |
| 0.0.4 | 12 Dec 2012 | none | non-standard | — | Details → |
| 0.0.3 | 12 Oct 2012 | none | non-standard | — | Details → |
| 0.0.2 | 12 Oct 2012 | none | non-standard | — | Details → |
| 0.0.1 | 12 Oct 2012 | none | non-standard | — | Details → |
All 12 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for mv
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About mv
Is mv safe to use?
Vulert has no vulnerabilities on record for mv in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is mv's Vulert package health score?
Vulert scores mv 52/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of mv affected?
No. 2.1.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of mv should I use?
2.1.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does mv have?
0 vulnerabilities are recorded for mv in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new mv vulnerabilities disclosed?
0 vulnerabilities were recorded for mv in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of mv are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor mv for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mv version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.