benchpress

v2.0.0-beta.17

Benchpress - a framework for e2e performance tests

MIT
Latest version published 5 years ago
    npm install benchpress
  

Package Health Score

56 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Small

Weekly Downloads (51)

Download trend
Dependents
12.53K
GitHub Stars
74.85K
Forks
19.62K
Contributors
400

Direct Usage Popularity

Uncommon

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

Based on project statistics from the GitHub repository for the npm package benchpress, we found that it has been starred 74,852 times, and that 12,533 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions

Version

Release Date

03/2014
04/2016

Direct Vulnerabilities

0.1.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0-beta.17
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.1.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0-beta.17
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.1.3
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0-beta.17
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like benchpress is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test benchpress
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
1.82K
Open PR
171
Last Release
5 years ago
Last Commit
7 days ago

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

Community

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

A good and healthy external contribution signal for benchpress project, which invites more than one hundred open source maintainers to collaborate on the repository.


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
7 Direct
Versions
71
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
2
TS Typings
No

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