1. Advisor
  2. JavaScript packages
  3. @quenty/elo

@quenty/elo

v7.16.0

Elo rating utility library. For more information about how to use this package see README

Latest version published 7 days 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

78 / 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
7.16.0 | 12/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
7.15.0 | 12/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.0 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.0.0 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.0 | 02/2024
  • 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 (194)

Download trend
GitHub Stars
426
Forks
126
Contributors
50

Direct Usage Popularity

The npm package @quenty/elo receives a total of 194 downloads a week. As such, we scored @quenty/elo popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @quenty/elo, we found that it has been starred 426 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
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
50
Funding
Yes

With more than 10 contributors for the @quenty/elo 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 @quenty/elo is missing a Code of Conduct.

Embed Package Health Score Badge

package health: 78/100 package health 78/100

Maintenance

Healthy

Commit Frequency

Open Issues
24
Open PR
30
Last Release
7 days ago
Last Commit
19 days ago

Further analysis of the maintenance status of @quenty/elo based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @quenty/elo demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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.

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
3 years
Dependencies
1 Direct
Versions
87
Install Size
31.6 kB
Dist-tags
2
# of Files
12
Maintainers
1
TS Typings
No

@quenty/elo 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.