@firebase/util
_NOTE: This is specifically tailored for Firebase JS SDK usage, if you are not a member of the Firebase team, please avoid using this package_
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 | large-new-source-files | AI (source-diff): Firebase SDK packages routinely add many source/dist files across versions as the SDK grows; this is expected behavior for @firebase/util in the Firebase monorepo. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): EAP pre-release version strings are a documented Firebase practice for early access program releases; not a malware indicator for this publisher. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual Firebase engineer maintainers in favor of google-wombot automation account is a standard organizational transition for Firebase SDK packages, not a takeover signal. | ai | |
| provenance | publisher-changed | AI (provenance): google-wombot is the official Firebase/Google automation publishing account; transition from individual engineer accounts to this bot is a standard Google practice for Firebase SDK packages. | ai | |
| provenance | no-provenance | AI (provenance): Firebase packages published via google-wombot automation consistently lack Sigstore provenance; this is a known pattern for this publisher. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): EAP/feature-branch pre-releases from the official Firebase publisher are expected to have irregular cadence; not indicative of account takeover. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency for Firebase packages compiled with TypeScript; stable false positive for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Firebase's postinstall script (node ./postinstall.js) is a long-standing, documented part of the Firebase JS SDK build process; stable for this package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @firebase/util is a scoped Google Firebase package with 3000+ days of history; Levenshtein match to 'uuid' is a clear false positive. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.12.1 | 1 / 4 | |
| 1.11.3 | 1 / 4 | |
| 1.10.3 | 1 / 3 | |
| 1.10.2 | 1 / 3 | |
| 1.10.1 | 1 / 3 | |
| 1.10.0 | 1 / 3 | |
| 1.9.7 | 1 / 3 | |
| 1.9.6 | 1 / 3 | |
| 1.9.5 | 1 / 3 | |
| 1.9.4 | 1 / 3 | |
| 1.9.3 | 1 / 3 | |
| 1.9.2 | 1 / 3 | |
| 1.9.1 | 1 / 3 | |
| 1.9.0 | 1 / 3 | |
| 1.8.0 | 1 / 3 | |
| 1.7.3 | 1 / 3 | |
| 1.7.2 | 1 / 3 | |
| 1.7.1 | 1 / 3 | |
| 1.7.0 | 1 / 3 | |
| 1.6.3 | 1 / 3 | |
| 1.6.2 | 1 / 3 | |
| 1.6.1 | 1 / 3 | |
| 1.6.0 | 1 / 3 | |
| 1.5.2 | 1 / 3 | |
| 1.5.1 | 1 / 3 | |
| 1.5.0 | 1 / 3 | |
| 1.4.3 | 1 / 3 | |
| 1.4.2 | 1 / 3 | |
| 1.4.1 | 1 / 3 | |
| 1.4.0 | 1 / 3 | |
| 1.3.0 | 1 / 3 | |
| 1.2.0 | 1 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.0 | 1 / 3 | |
| 0.4.1 | 1 / 3 | |
| 0.4.0 | 1 / 3 | |
| 0.3.4 | 1 / 3 |
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
2 findingsThis version was published by a different npm account than previous versions on 2024-03-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
2 findingsThis version was published by a different npm account than previous versions on 2024-02-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.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 2022-10-27. This could indicate a legitimate maintainer transition or an account compromise.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.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 2022-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.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 2022-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.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 2022-04-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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 2022-01-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.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-03-31. This could indicate a legitimate maintainer transition or an account compromise.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.