@vates/async-each

v1.0.0

Run async fn for each item in (async) iterable For more information about how to use this package see README

Latest version published 2 years ago
License: ISC

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

64 / 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
1.0.0 | 07/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0 | 11/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
ISC
Security Policy
Yes

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

Limited

Weekly Downloads (26)

Download trend
GitHub Stars
782
Forks
264
Contributors
-

Direct Usage Popularity

Occasionally

The npm package @vates/async-each receives a total of 26 downloads a week. As such, we scored @vates/async-each popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @vates/async-each, we found that it has been starred 782 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
0
Funding
No

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 64/100 package health 64/100

Maintenance

Inactive

Commit Frequency

Open Issues
255
Open PR
92
Last Release
2 years ago
Last Commit
9 days ago

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

Package

Node.js Compatibility
>=8.10

Age
3 years
Dependencies
0 Direct
Versions
3
Install Size
5.77 kB
Dist-tags
1
# of Files
3
Maintainers
12
TS Typings
No

@vates/async-each 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.