@mdn/browser-compat-data 7.3.12

Browser compatibility data provided by MDN Web Docs

@mdn/browser-compat-data@7.3.12 was published on 2026-04-17. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @mdn/browser-compat-data versions · Permanent reference to 7.3.12 · Latest release

Package specifications

Version7.3.12
License declarationCC0-1.0
Published2026-04-17T21:17:03.018Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size18633.33 KiB
Published file count8
Package typeNot declared
ES module entryNot declared
Default entrydata.json
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars5777
Repository forks2678

Install @mdn/browser-compat-data 7.3.12

npm install @mdn/browser-compat-data@7.3.12
pnpm add @mdn/browser-compat-data@7.3.12
yarn add @mdn/browser-compat-data@7.3.12

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Maintained10/10 — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
SAST6/10 — SAST tool is not run on all commits -- score normalized to 6

Evidence and freshness