alert

ronin

v0.3.11

Libary to build shining CLI tools

MIT
Latest version published 6 years ago
    npm install ronin
  

Package Health Score

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

Popularity

Limited
Download trend

Weekly Downloads (121)

Dependents
35
GitHub Stars
300
Forks
16
Contributors
2

The npm package ronin receives a total of 121 downloads a week. As such, we scored ronin popularity level to be Limited.

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

11/2014
12/2014
01/2015
08/2015

Direct Vulnerabilities

0.0.1
  • 0
    H
  • 0
    M
  • 0
    L
0.1.8
  • 0
    H
  • 0
    M
  • 0
    L
0.2.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.3.11
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.1
  • 0
    H
  • 0
    M
  • 0
    L
0.1.8
0.2.0
Popular
0.3.11

License Risk

0.0.1
  • 0
    H
  • 0
    M
  • 0
    L
0.1.8
  • 0
    H
  • 0
    M
  • 0
    L
0.2.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.3.11
  • 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 ronin 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 ronin
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of ronin 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 ronin 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
2
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 39/100 package health 39/100

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
10 Direct
Versions
24
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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