error

v10.4.0

Custom errors

Unknown
Latest version published 2 years ago
    npm install error
  

Package Health Score

76 / 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
10.4.0 | 05/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.3.0 | 05/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
7.2.1 | 11/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.4.3 | 05/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.2.0 | 05/2015
  • 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.

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

Popularity

Influential project

Weekly Downloads (1,448,045)

Download trend
Dependents
178
GitHub Stars
121
Forks
17
Contributors
8

Direct Usage Popularity

TOP 10%

The npm package error receives a total of 1,448,045 downloads a week. As such, we scored error popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package error, we found that it has been starred 121 times, and that 178 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
8
Funding
No

This project has seen only 10 or less contributors.

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

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


Embed Package Health Score Badge

package health: 76/100 package health 76/100

Maintenance

Sustainable

Commit Frequency

Open Issues
0
Open PR
0
Last Release
2 years ago
Last Commit
2 months ago

Further analysis of the maintenance status of error 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 error 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
11 years
Dependencies
0 Direct
Versions
49
Install Size
51.9 kB
Dist-tags
2
# of Files
14
Maintainers
2
TS Typings
No

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