cfork

v2.0.0

cluster fork and restart easy way For more information about how to use this package see README

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

74 / 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
2.0.0 | 12/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.11.0 | 05/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.10.0 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.9.0 | 05/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.8.0 | 06/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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

Recognized

Weekly Downloads (20,949)

Download trend
GitHub Stars
156
Forks
22
Contributors
20

Direct Usage Popularity

TOP 30%

The npm package cfork receives a total of 20,949 downloads a week. As such, we scored cfork popularity level to be Recognized.

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

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
No
Contributors
20
Funding
No

With more than 10 contributors for the cfork 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 cfork is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 74/100 package health 74/100

Maintenance

Sustainable

Commit Frequency

Open Issues
0
Open PR
0
Last Release
7 days ago
Last Commit
7 months ago

Further analysis of the maintenance status of cfork based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that cfork demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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

Age
10 years
Dependencies
1 Direct
Versions
24
Install Size
72.8 kB
Dist-tags
1
# of Files
11
Maintainers
3
TS Typings
No

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