mdn-browser-compat-data CC0-1.0 43 versions

mdn-browser-compat-data

npm Repository Homepage

Browser compatibility data provided by MDN Web Docs

43

Versions

CC0-1.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

escattoneddbeckschalkneethlingpeterbemdn-npmjs

Keywords

browser-compat-databrowsercompatibilitydatamdnmozilla

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Transition from 'mdn' to a team of known MDN contributors (ddbeck, mdn-npmjs, peterbe, schalkneethling) is a documented org-level handoff, not a hostile takeover. Publisher ddbeck has 883 approved packages.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from 'mdn' to 'ddbeck' reflects a legitimate MDN org transition; ddbeck is a long-standing, well-vetted npm publisher with 883 approved packages.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of 'mdn' account is part of the same legitimate org-level transition to named MDN contributors.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in index.js is used to load .json compat data files by path — core library functionality, not arbitrary code execution.	ai	2026/04/23
semgrep	semgrep:child-process-import	AI (semgrep): child_process is used only in dev/build scripts (scripts/fix-format.js), not in runtime code or install hooks. Stable false positive for this package.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): MDN Web Docs is a large Mozilla project; maintainer additions are routine team changes. No suspicious code changes accompany this addition.	ai	2026/04/23

Versions (showing 43 of 143)

Version	Deps	Published
0.0.43	1 / 2	2018-07-19
0.0.42	1 / 2	2018-07-12
0.0.41	1 / 2	2018-07-10
0.0.40	1 / 2	2018-06-28
0.0.39	1 / 2	2018-06-21
0.0.38	1 / 2	2018-06-07
0.0.37	1 / 2	2018-05-31
0.0.36	1 / 2	2018-05-24
0.0.35	1 / 2	2018-05-17
0.0.34	1 / 2	2018-05-03
0.0.33	1 / 2	2018-04-26
0.0.32	1 / 2	2018-04-19
0.0.31	1 / 1	2018-04-12
0.0.30	1 / 1	2018-04-05
0.0.29	1 / 1	2018-03-21
0.0.28	1 / 1	2018-03-15
0.0.27	1 / 1	2018-03-08
0.0.26	1 / 1	2018-03-01
0.0.25	1 / 1	2018-02-22
0.0.24	1 / 1	2018-02-14
0.0.23	1 / 1	2018-02-12
0.0.22	1 / 1	2018-02-06
0.0.21	1 / 1	2018-01-25
0.0.20	1 / 1	2018-01-18
0.0.19	1 / 1	2018-01-11
0.0.18	1 / 1	2018-01-04
0.0.17	1 / 1	2017-12-18
0.0.16	1 / 1	2017-12-04
0.0.15	1 / 1	2017-11-27
0.0.14	1 / 1	2017-11-13
0.0.13	1 / 1	2017-11-06
0.0.12	1 / 1	2017-10-30
0.0.11	1 / 1	2017-10-23
0.0.10	1 / 1	2017-10-16
0.0.9	1 / 1	2017-10-09
0.0.8	1 / 1	2017-10-02
0.0.7	1 / 1	2017-09-25
0.0.6	1 / 1	2017-09-18
0.0.5	1 / 1	2017-09-07
0.0.4	1 / 1	2017-08-24
0.0.3	1 / 1	2017-06-22
0.0.2	1 / 0	2017-06-06
0.0.1	1 / 0	2017-05-18

v0.0.43

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.