check-error

v1.0.2

Error comparison and information related utility for node and the browser

MIT
Latest version published over 4 years ago
    npm install check-error
  

Package Health Score

56 / 100
  • Popularity
    Influential project
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited

Popularity

Influential project
Weekly Downloads (2,885,411)
Dependents
42
GitHub Stars
7
Forks
4
Contributors
3

The npm package check-error receives a total of 2,885,411 downloads a week. As such, we scored check-error popularity level to be Influential project.

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

Security

No known security issues

Security and license risk for recent versions


Direct Vulnerabilities

1.0.0
1.0.1
1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.0
1.0.1
1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

1.0.0
1.0.1
1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like check-error is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test check-error
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
0
Merged PR
9
Open PR
3
Last Commit
4 years ago

Further analysis of the maintenance status of check-error 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 check-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.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
3
Funding
No
License
MIT

This project has seen only 10 or less contributors.

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

Package

Node.js Compatibility
*

Age
4 years
Dependencies
0 Direct / 0 Total
Versions
3
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

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