combine-errors

v3.0.3

Combine errors into one For more information about how to use this package see README

Latest version published 8 years ago
License: Unknown

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

44 / 100

Security

Security review needed
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
3.0.3 | 06/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0 | 03/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 03/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Unknown
Alert

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.

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

Popular

Weekly Downloads (239,156)

Download trend
GitHub Stars
31
Forks
2
Contributors
-

Direct Usage Popularity

TOP 30%

The npm package combine-errors receives a total of 239,156 downloads a week. As such, we scored combine-errors popularity level to be Popular.

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

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that combine-errors is missing a LICENSE file.


Embed Package Health Score Badge

package health: 44/100 package health 44/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
8 years ago
Last Commit
8 years ago

Further analysis of the maintenance status of combine-errors 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 combine-errors 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
not defined

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

combine-errors 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.