@firebase/messaging
This is the Firebase Cloud Messaging component of the Firebase JS SDK.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/browser/HeadlessChrome 65.0.3325 (Linux 0.0.0)/prettify.js | AI (source-diff): This is the well-known Google Code Prettify syntax highlighter in minified form, bundled as a Karma test coverage report artifact. Benign and stable for this Firebase SDK package. | ai | |
| provenance | no-provenance | AI (provenance): google-wombot/Firebase packages do not currently publish Sigstore provenance; this is consistent across all Firebase SDK releases and not a meaningful risk signal. | ai | |
| dependencies | unvetted-dep:@firebase/installations | AI (dependencies): @firebase/installations is a core Firebase SDK package from the same Google org; unvetted status is a pipeline gap, not a real risk for this well-established ecosystem. | ai | |
| dependencies | unvetted-dep:@firebase/util | AI (dependencies): @firebase/util is a core Firebase SDK utility package from the same Google org; unvetted status is a pipeline gap, not a real risk for this well-established ecosystem. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): tslib is Microsoft's TypeScript runtime helpers library — a standard, trusted dependency for TypeScript-compiled packages. No risk. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from jshcrowthe to feiyang.chen in 2018 reflects a legitimate Firebase/Google team transition; both are long-standing Firebase team members. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): feiyang.chen and hiranya911 are established Firebase/Google team members; maintainer additions reflect legitimate internal team changes. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; its use as an implicit dependency is expected in compiled TypeScript Firebase SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and missing keywords are typical of monorepo sub-bundle packages (messaging-sw); not indicative of spam for an official Google Firebase SDK. | ai | |
| phantom-deps | phantom-dep:@firebase/messaging-interop-types | AI (phantom-deps): Same-org type-only package used as an interop types declaration; expected pattern for Firebase monorepo sub-packages. | ai |
Versions (showing 51 of 146)
| Version | Deps | Published |
|---|---|---|
| 0.12.26 | 6 / 6 | |
| 0.12.25 | 6 / 6 | |
| 0.12.24 | 6 / 6 | |
| 0.12.23 | 6 / 6 | |
| 0.12.22 | 6 / 6 | |
| 0.12.21 | 6 / 6 | |
| 0.12.20 | 6 / 6 | |
| 0.12.19 | 6 / 6 | |
| 0.12.18 | 6 / 6 | |
| 0.12.17 | 6 / 6 | |
| 0.12.16 | 6 / 6 | |
| 0.12.15 | 6 / 6 | |
| 0.12.14 | 6 / 6 | |
| 0.12.13 | 6 / 6 | |
| 0.12.12 | 6 / 6 | |
| 0.12.11 | 6 / 6 | |
| 0.12.10 | 6 / 6 | |
| 0.12.9 | 6 / 6 | |
| 0.12.8 | 6 / 6 | |
| 0.12.7 | 6 / 6 | |
| 0.12.6 | 6 / 6 | |
| 0.12.5 | 6 / 6 | |
| 0.12.4 | 6 / 6 | |
| 0.12.3 | 6 / 6 | |
| 0.12.2 | 6 / 6 | |
| 0.12.1 | 6 / 6 | |
| 0.12.0 | 6 / 6 | |
| 0.11.0 | 6 / 6 | |
| 0.10.0 | 6 / 6 | |
| 0.9.19 | 6 / 6 | |
| 0.9.18 | 6 / 6 | |
| 0.9.17 | 6 / 6 | |
| 0.9.16 | 6 / 6 | |
| 0.9.15 | 6 / 6 | |
| 0.9.14 | 6 / 6 | |
| 0.9.13 | 6 / 6 | |
| 0.9.12 | 5 / 6 | |
| 0.9.11 | 5 / 6 | |
| 0.9.10 | 5 / 6 | |
| 0.9.9 | 6 / 6 | |
| 0.9.8 | 6 / 6 | |
| 0.9.7 | 6 / 6 | |
| 0.9.6 | 6 / 6 | |
| 0.9.5 | 6 / 6 | |
| 0.9.4 | 6 / 6 | |
| 0.9.3 | 6 / 6 | |
| 0.9.2 | 6 / 6 | |
| 0.9.1 | 6 / 6 | |
| 0.9.0 | 6 / 6 | |
| 0.8.0 | 6 / 5 | |
| 0.7.15 | 6 / 5 |
v0.12.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-03-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-01-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-01-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-01-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-09-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-25. This could indicate a legitimate maintainer transition or an account compromise.
v0.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-19. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.