next-with-error

v1.2.0

Next.js HoC to render the Error page and send the correct HTTP status code from any page

MIT
Latest version published 1 year ago
    npm install next-with-error
  

Package Health Score

51 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Limited
Download trend

Weekly Downloads (857)

Dependents
0
GitHub Stars
27
Forks
1
Contributors

The npm package next-with-error receives a total of 857 downloads a week. As such, we scored next-with-error popularity level to be Limited.

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

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.1.1
1.1.1
1.2.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.1.1
1.1.1
1.2.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.1.1
1.1.1
1.2.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

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


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

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test next-with-error
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
3
Open PR
1
Last Release
1 year ago
Last Commit
3 months ago

Further analysis of the maintenance status of next-with-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 next-with-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
0
Funding
Yes

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
0 Direct
Versions
7
Install Size
27.8 kB
Dist-tags
1
# of Files
6
Maintainers
1
TS Typings
No

next-with-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.