next-runtime

v2.4.2

handler to improve data handling in Next.js getServerSideProps For more information about how to use this package see README

Latest version published 20 days ago
License: MIT

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

66 / 100

Security

No known security issues
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
2.4.2 | 10/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.4.1 | 07/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.3.6 | 04/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.0 | 09/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.4.0 | 09/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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

Limited

Weekly Downloads (106)

Download trend
GitHub Stars
591
Forks
19
Contributors
8

Direct Usage Popularity

TOP 5%

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

Based on project statistics from the GitHub repository for the npm package next-runtime, we found that it has been starred 591 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

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


Embed Package Health Score Badge

package health: 66/100 package health 66/100

Maintenance

Sustainable

Commit Frequency

Open Issues
11
Open PR
0
Last Release
20 days ago
Last Commit
11 months ago

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

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

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
3 years
Dependencies
20 Direct
Versions
25
Install Size
1.45 MB
Dist-tags
1
# of Files
135
Maintainers
1
TS Typings
No

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