1. Advisor
  2. JavaScript packages
  3. browser-capabilities

browser-capabilities

v1.1.4

Detect browser capabilities from a user agent string. For more information about how to use this package see README

Latest version published 5 years ago
License: BSD-3-Clause
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

60 / 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
1.1.4 | 05/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 04/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.2.2 | 01/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.1 | 08/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-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.

Get started free

Popularity

Small

Weekly Downloads (4,088)

Download trend
GitHub Stars
430
Forks
200
Contributors
170

Direct Usage Popularity

TOP 30%

The npm package browser-capabilities receives a total of 4,088 downloads a week. As such, we scored browser-capabilities popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package browser-capabilities, we found that it has been starred 430 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
No
Code of Conduct
No
Contributors
170
Funding
No

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

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

Embed Package Health Score Badge

package health: 60/100 package health 60/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
708
Open PR
123
Last Release
5 years ago
Last Commit
3 years ago

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

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
>=8.0
Age
7 years
Dependencies
2 Direct
Versions
12
Install Size
24.5 kB
Dist-tags
1
# of Files
11
Maintainers
10
TS Typings
Yes

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