forever-binom

v0.10.11

A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever) For more information about how to use this package see README

Latest version published 9 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

36 / 100

Explore Similar Packages

Security

Security review needed
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
0.10.11 | 02/2014
Popular
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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

Small

Weekly Downloads (2)

Download trend
GitHub Stars
13.7K
Forks
986
Contributors
90

Direct Usage Popularity


The npm package forever-binom receives a total of 2 downloads a week. As such, we scored forever-binom popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package forever-binom, we found that it has been starred 13,704 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
90
Funding
No

With more than 10 contributors for the forever-binom repository, this is possibly a sign for a growing and inviting community.

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


Embed Package Health Score Badge

package health: 36/100 package health 36/100

Maintenance

Inactive

Commit Frequency

Open Issues
313
Open PR
24
Last Release
9 years ago
Last Commit
11 months ago

Further analysis of the maintenance status of forever-binom 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 forever-binom 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
>= 0.8.x

Age
9 years
Dependencies
12 Direct
Versions
2
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

forever-binom 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.