for-each

v0.3.3

A better forEach For more information about how to use this package see README

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

68 / 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
0.3.3 | 06/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0 | 09/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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

Influential project

Weekly Downloads (31,164,491)

Download trend
GitHub Stars
21
Forks
6
Contributors
3

Direct Usage Popularity

TOP 5%

The npm package for-each receives a total of 31,164,491 downloads a week. As such, we scored for-each popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package for-each, we found that it has been starred 21 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
3
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 68/100 package health 68/100

Maintenance

Sustainable

Commit Frequency

Open Issues
0
Open PR
0
Last Release
6 years ago
Last Commit
1 month ago

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

An important project maintenance signal to consider for for-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
not defined

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

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