browser-perf

v1.4.11

Measure browser rendering performance metrics

BSD-2-Clause
Latest version published 6 years ago
    npm install browser-perf
  
We couldn't find any similar packages Browse all packages

Package Health Score

42 / 100

Security

Security review needed
Powered by Snyk
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.4.11 | 06/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.3 | 07/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.21 | 09/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.11 | 01/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-2-Clause
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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test browser-perf
Get started free

Popularity

Small

Weekly Downloads (1,830)

Download trend
Dependents
6
GitHub Stars
934
Forks
67
Contributors
10

Direct Usage Popularity

Occasionally

The npm package browser-perf receives a total of 1,830 downloads a week. As such, we scored browser-perf popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package browser-perf, we found that it has been starred 934 times, and that 6 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.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
10
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like browser-perf is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 42/100 package health 42/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
16
Open PR
2
Last Release
6 years ago
Last Commit
5 years ago

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

Package

Node.js Compatibility
not defined

Age
9 years
Dependencies
11 Direct
Versions
67
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

browser-perf 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.