next-plugins

v1.0.3

Provides a cleaner API for enabling and configuring plugins for next.js For more information about how to use this package see README

Latest version published 5 years 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

51 / 100

Explore Similar Packages

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
1.0.3 | 03/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0 | 03/2018
  • 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 (0)

Download trend
Dependents
122
GitHub Stars
678
Forks
15
Contributors
3

Direct Usage Popularity


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

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

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
3
Funding
No

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Maintenance

Inactive
deprecated

Commit Frequency

No Recent Commits
Open Issues
18
Open PR
11
Last Release
5 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of next-plugins 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-plugins 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
5 years
Dependencies
0 Direct
Versions
5
Install Size
2.43 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

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