@firebase/messaging 0.1.9

This is the messaging component for the Firebase JS SDK. It has a peer dependency on the [`@firebase/app`](https://npm.im/@firebase/app) package on NPM. This package is included by default in the [`firebase`](https://npm.im/firebase) wrapper package.

@firebase/messaging@0.1.9 was published on 2018-02-02. Its manifest declares 2 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @firebase/messaging versions · Permanent reference to 0.1.9 · Latest release

Package specifications

Version0.1.9
License declarationApache-2.0
Published2018-02-02T00:02:17.539Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entrydist/esm/index.js
Default entrydist/cjs/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars5154
Repository forks1039

Install @firebase/messaging 0.1.9

npm install @firebase/messaging@0.1.9
pnpm add @firebase/messaging@0.1.9
yarn add @firebase/messaging@0.1.9

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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.

Maintained10/10 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Code-Review8/10 — Found 24/27 approved changesets -- score normalized to 8
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions7/10 — detected GitHub workflow tokens with excessive permissions
License9/10 — license file detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies10/10 — all dependencies are pinned
Security-Policy10/10 — security policy file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Fuzzing0/10 — project is not fuzzed
SAST7/10 — SAST tool is not run on all commits -- score normalized to 7

Evidence and freshness