1. Advisor
  2. JavaScript packages
  3. @stablelib/benchmark

@stablelib/benchmark

v2.0.0

StableLib benchmarking suite For more information about how to use this package see README

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

65 / 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.0.0 | 06/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 05/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.5.0 | 05/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.2.5 | 04/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.1 | 04/2017
  • 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 (448)

Download trend
GitHub Stars
174
Forks
36
Contributors
20

Direct Usage Popularity

The npm package @stablelib/benchmark receives a total of 448 downloads a week. As such, we scored @stablelib/benchmark popularity level to be Limited.

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

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

How about a good first contribution to this project? It seems that @stablelib/benchmark is missing a README file.

Embed Package Health Score Badge

package health: 65/100 package health 65/100

Maintenance

Sustainable

Commit Frequency

Open Issues
5
Open PR
3
Last Release
5 months ago
Last Commit
26 days ago

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

We found that @stablelib/benchmark demonstrates a positive version release cadence with at least one new version released in the past 12 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
8 years
Dependencies
0 Direct
Versions
7
Install Size
17.4 kB
Dist-tags
1
# of Files
8
Maintainers
1
TS Typings
Yes

@stablelib/benchmark 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.