co-with-promise

v4.6.0

generator async control flow goodness

MIT
Latest version published 6 years ago
    npm install co-with-promise
  

Package Health Score

58 / 100

Popularity

Popular

Weekly Downloads (39,732)

Download trend
Dependents
13.06K
GitHub Stars
11.58K
Forks
813
Contributors
60

Direct Usage Popularity

TOP 30%

The npm package co-with-promise receives a total of 39,732 downloads a week. As such, we scored co-with-promise popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package co-with-promise, we found that it has been starred 11,583 times, and that 13,056 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

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

11/2015

Direct Vulnerabilities

Popular
4.6.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
4.6.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
4.6.0
  • 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 co-with-promise 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 co-with-promise
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
30
Open PR
15
Last Release
6 years ago
Last Commit
5 years ago

Further analysis of the maintenance status of co-with-promise 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 co-with-promise 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.

Community

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

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


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Package

Node.js Compatibility
>= 0.10.0

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

co-with-promise 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.