npmpackage.info

Gathering detailed insights and metrics for map-to-chrome

Other packages similar to map-to-chrome

source-map-support

0.5.21

Fixes stack traces for files with source maps

source-map-explorer

2.5.3

Analyze and debug space usage through source maps

source-map-js

1.2.1

Generates and consumes source maps

chrome-launcher

1.1.2

Launch latest Chrome with the Devtools Protocol port open

Gathering detailed insights and metrics for map-to-chrome

map-to-chrome

Map versions of Chromium-based browsers to their equivalent Chrome versions.

0.0.3

MIT

JavaScript

2,870,274 1.7

Installations

npm install map-to-chrome

Pull Requests

Open

1

Total

3

Closed

0

Merged

2

Issues

Open

3

Total

3

Closed

0

Releases

Unable to fetch releases

Developer

dmfrancisco

Developer Guide

BETA

Module System

Unable to determine the module system for this package.

Min. Node Version

Typescript Support

No

Node Version

10.10.0

NPM Version

6.4.1 Statistics

18 Stars

29 Commits

5 Forks

3 Watching

1 Branches

8 Contributors

Updated on 30 Aug 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

2,870,274

Last day

19.7%

5,695

Compared to previous day

Last week

17%

29,698

Compared to previous week

Last month

12.1%

111,170

Compared to previous month

Last year

189.6%

1,646,906

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

d3 jsdom json-stringify-pretty-compact lodash.isequal lodash.sortby svgo

Versions

Map versions of Chromium-based browsers to their equivalent Chrome versions.

About this project

This package was created for Browserslist-GA, a package that lets you use your own analytics with Browserslist. Browserslist uses data from caniuse.com and so only supports the same browsers.

There are some other popular browsers however in some regions that are Chromium-based. This package maps versions of those browsers to their equivalent Chrome/Chromium versions so they can be tracked when used with tools such as Browserslist-GA.

How does it work

Let's take the Yandex Browser (or YaBrowser), a popular browser in russian-speaking countries, as an example. The Yandex Browser UA strings look like this:

Mozilla/5.0 (<platform>) AppleWebKit/<webkit-rev> (KHTML, like Gecko) Chrome/<chrome-version> YaBrowser/<yabrowser-version> Safari/<webkit-rev>

Platform can be Windows, Linux, macOS or Android (on iOS is different since all browsers use Safari's WebKit as the underlying engine). This repository contains a file named yabrowser.json that maps YaBrowser major and minor versions to the equivalent Chrome versions. The format is as follows:

[<yabrowser-major>, <yabrowser-minor>, <chrome-major>, <chrome-minor>]

Supported browsers

Yandex Browser (or YaBrowser), a popular browser in russian-speaking countries
Cốc Cốc Browser, the 2nd most popular browser in Vietnam
QQ Browser for Windows, the 2nd most popular desktop browser in China
Electron, a framework to develop cross-platform desktop applications

Supported browsers table

Contributing

If you know more about any of these browsers or have a better way to achieve this, please let us know by opening an issue or contacting the email in my GitHub profile.

If you have data for another Chromium-based browser, please open a pull request. Help us keep the data updated by contributing with new versions, also by opening a pull request. Thank you in advance!

Credits

The data for YaBrowser was initially extracted from Browserslist-GA and is based on this pull request by @Vasfed.
Electron data was completed and confirmed thanks to the electron-to-chromium project.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.7

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More