benchmark

v2.1.4

A benchmarking library that supports high-resolution timers & returns statistically significant results. For more information about how to use this package see README

Latest version published 8 years ago

License: MIT

NPM

GitHub

Package Health Score

61 / 100

security
No known security issues
popularity
Influential project
maintenance
Inactive
community
Sustainable

Explore Similar Packages

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.1.4	\|	03/2017	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.0	\|	01/2016		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.0	\|	08/2012		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.3.0	\|	12/2011		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.2.2	\|	06/2011		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

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

Influential project

Weekly Downloads (269,185)

GitHub Stars: 5.48K
Forks: 331
Contributors: 20

Direct Usage Popularity

The npm package benchmark receives a total of 269,185 downloads a week. As such, we scored benchmark popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package benchmark, we found that it has been starred 5,483 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: Yes
Code of Conduct: No
Contributors: 20
Funding: No

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

Embed Package Health Score Badge

Maintenance

Inactive

archived

Commit Frequency

No Recent Commits

Open Issues: 40
Open PR: 12
Last Release: 8 years ago
Last Commit: 6 years ago

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

Check your package.json

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

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 14 years
Dependencies: 2 Direct
Versions: 27
Install Size: 0 B
Dist-tags: 1
# of Files: 0
Maintainers: 2
TS Typings: Yes

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.

Not sure how to use benchmark?

To help you get started, we've collected the most common ways that benchmark is being used within popular public projects.

bramstein / hypher / test / benchmark.js View on Github

var Benchmark = require('benchmark'),
    Hypher = require('../lib/hypher'),
    suite = new Benchmark.Suite('warm cache'),
    data = require('./data'),
    words = data.words,
    language = data.language,
    assert = require('assert'),
    dictionary = {},
    Hyphenator = require('./Hyphenator.js');

var result = {};

// Create the dictionary of words we're using to test
words.forEach(function (word) {
    var w = word.split('=');
    dictionary[w.join('')] = w;
});

Hyphenator.config({

View more ways to use benchmark

Benchmark.js v2.1.4

A robust benchmarking library that supports high-resolution timers & returns statistically significant results. As seen on jsPerf.

Documentation

API Documentation

Download

Development source

Installation

Benchmark.js’ only hard dependency is lodash. Include platform.js to populate Benchmark.platform.

In a browser:

In an AMD loader:

require({
  'paths': {
    'benchmark': 'path/to/benchmark',
    'lodash': 'path/to/lodash',
    'platform': 'path/to/platform'
  }
},
['benchmark'], function(Benchmark) {/*…*/});

Using npm:

$ npm i --save benchmark

In Node.js:

var Benchmark = require('benchmark');

Optionally, use the microtime module by Wade Simmons:

npm i --save microtime

Usage example:

var suite = new Benchmark.Suite;

// add tests
suite.add('RegExp#test', function() {
  /o/.test('Hello World!');
})
.add('String#indexOf', function() {
  'Hello World!'.indexOf('o') &gt; -1;
})
// add listeners
.on('cycle', function(event) {
  console.log(String(event.target));
})
.on('complete', function() {
  console.log('Fastest is ' + this.filter('fastest').map('name'));
})
// run async
.run({ 'async': true });

// logs:
// =&gt; RegExp#test x 4,161,532 +-0.99% (59 cycles)
// =&gt; String#indexOf x 6,139,623 +-1.00% (131 cycles)
// =&gt; Fastest is String#indexOf

Support

Tested in Chrome 54-55, Firefox 49-50, IE 11, Edge 14, Safari 9-10, Node.js 6-7, & PhantomJS 2.1.1.

BestieJS

Benchmark.js is part of the BestieJS “Best in Class” module collection. This means we promote solid browser/environment support, ES5+ precedents, unit testing, & plenty of documentation.

benchmark dependencies

lodash platform

benchmark development dependencies

coveralls docdown istanbul qunit-extras qunitjs requirejs

FAQs

What is benchmark?

A benchmarking library that supports high-resolution timers & returns statistically significant results. Visit Snyk Advisor to see a full health score report for benchmark, including popularity, security, maintenance & community analysis.

Is benchmark popular?

The npm package benchmark receives a total of 269,185 weekly downloads. As such, benchmark popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is benchmark well maintained?

We found indications that benchmark is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is benchmark safe to use?

The npm package benchmark was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 December-2024, at 13:24 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP