each-async

v2.0.0

Async concurrent iterator (async forEach)

MIT
Latest version published 1 year ago
    npm install each-async
  
We couldn't find any similar packages Browse all packages

Package Health Score

56 / 100

Security

No known security issues
Powered by Snyk
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 | 05/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.1 | 12/2014
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.3 | 04/2014
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test each-async
Get started free

Popularity

Popular

Weekly Downloads (232,727)

Download trend
Dependents
219
GitHub Stars
108
Forks
8
Contributors
4

Direct Usage Popularity

TOP 30%

The npm package each-async receives a total of 232,727 downloads a week. As such, we scored each-async popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package each-async, we found that it has been starred 108 times, and that 219 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.

Community

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

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive
deprecated

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
1 year ago
Last Commit
2 years ago

Further analysis of the maintenance status of each-async 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 each-async 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.10.0

Age
9 years
Dependencies
2 Direct
Versions
9
Install Size
4.36 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

each-async 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.