win-release

v3.0.0

Get the name of a Windows version from the release number: `5.1.2600` → `XP` For more information about how to use this package see README

Latest version published 4 years 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

56 / 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
3.0.0 | 05/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0 | 07/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.1 | 09/2015
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 08/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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

Popular

Weekly Downloads (323,534)

Download trend
Dependents
28
GitHub Stars
33
Forks
14
Contributors
10

Direct Usage Popularity

TOP 30%

The npm package win-release receives a total of 323,534 downloads a week. As such, we scored win-release popularity level to be Popular.

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

Community

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

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
4
Open PR
0
Last Release
4 years ago
Last Commit
11 months ago

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

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
>=6

Age
8 years
Dependencies
1 Direct
Versions
7
Install Size
4.45 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

win-release 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.