pretty-error

v2.1.2

See nodejs errors with less clutter

MIT
Latest version published 4 days ago
    npm install pretty-error
  

Package Health Score

81 / 100
  • Popularity
    Influential project
  • Maintenance
    Healthy
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Influential project
Weekly Downloads (6,278,897)
Dependents
748
GitHub Stars
1.35K
Forks
40
Contributors
8

The npm package pretty-error receives a total of 6,278,897 downloads a week. As such, we scored pretty-error popularity level to be Influential project.

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

2.1.0
2.1.1
2.2.0-rc.1
3.0.2
2.1.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

2.1.0
2.1.1
2.2.0-rc.1
3.0.2
2.1.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

2.1.0
2.1.1
2.2.0-rc.1
3.0.2
2.1.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 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 pretty-error is missing a security policy.

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

Maintenance

Healthy
Commit Frequency
Open Issues
14
Merged PR
8
Open PR
2
Last Commit
4 days ago

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

We found that pretty-error demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
8
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 pretty-error is missing a Code of Conduct.

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
2 Direct / 24 Total
Versions
5
Install Size
57.8 kB
Dist-tags
2
# of Files
17
Maintainers
1
TS Typings
No

We detected a total of 24 direct & transitive dependencies for pretty-error. See the full dependency tree of pretty-error

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