1. Advisor
  2. JavaScript packages
  3. fixngxe

fixngxe

v8.0.0

[![AbstruseCI](https://ci.bleenco.io/badge/11)](https://ci.bleenco.io/repo/11) For more information about how to use this package see README

Latest version published 5 years ago
License: MIT
NPM
GitHub

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

42 / 100

Explore Similar Packages

Security

Security review needed
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
8.0.0 | 02/2020
Popular
  • 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
GitHub Stars
757
Forks
348
Contributors
70

Direct Usage Popularity

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

Based on project statistics from the GitHub repository for the npm package fixngxe, we found that it has been starred 757 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
No
Code of Conduct
No
Contributors
70
Funding
No

With more than 10 contributors for the fixngxe repository, this is possibly a sign for a growing and inviting community.

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

Embed Package Health Score Badge

package health: 42/100 package health 42/100

Maintenance

Inactive

Commit Frequency

Open Issues
117
Open PR
10
Last Release
5 years ago
Last Commit
12 months ago

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

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
5 years
Dependencies
11 Direct
Versions
2
Install Size
77.2 kB
Dist-tags
1
# of Files
52
Maintainers
1
TS Typings
No

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