winreg

v1.2.5

provides access to the windows registry through the REG tool For more information about how to use this package see README

Latest version published 1 year ago
License: BSD-2-Clause

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

60 / 100

Explore Similar Packages

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
1.2.5 | 10/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.1 | 04/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.18 | 02/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-2-Clause
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

Popular

Weekly Downloads (227,713)

Download trend
GitHub Stars
210
Forks
61
Contributors
-

Direct Usage Popularity

TOP 5%

The npm package winreg receives a total of 227,713 downloads a week. As such, we scored winreg popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package winreg, we found that it has been starred 210 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

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

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 60/100 package health 60/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
13
Open PR
5
Last Release
1 year ago
Last Commit
1 year ago

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

Package

Node.js Compatibility
not defined

Age
12 years
Dependencies
0 Direct
Versions
29
Install Size
44.1 kB
Dist-tags
1
# of Files
6
Maintainers
2
TS Typings
Yes

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