forgeeditor

v2.0.0

undefined For more information about how to use this package see README

Latest version published 2 years ago
License: CC0-1.0

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

57 / 100

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
1.0.100 | 01/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0 | 01/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
CC0-1.0
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

Small

Weekly Downloads (8)

Download trend
GitHub Stars
11.17K
Forks
4.94K
Contributors
60

Direct Usage Popularity


The npm package forgeeditor receives a total of 8 downloads a week. As such, we scored forgeeditor popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package forgeeditor, we found that it has been starred 11,174 times.

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

Community

Active
Readme.md
No
Contributing.md
No
Code of Conduct
Yes
Contributors
60
Funding
No

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

How about a good first contribution to this project? It seems that forgeeditor is missing a README file.


Embed Package Health Score Badge

package health: 57/100 package health 57/100

Maintenance

Inactive

Commit Frequency

Open Issues
16
Open PR
0
Last Release
2 years ago
Last Commit
25 days ago

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

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.

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
42 Direct
Versions
97
Install Size
24.8 MB
Dist-tags
1
# of Files
271
Maintainers
1
TS Typings
No

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