← Home

@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_

100
Versions
Apache-2.0
License
Yes
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

firebase-opsfeiyang.chengoogle-wombotchholland

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 108)

Hide prereleases
Version Deps Published
1.15.1 1 / 4
1.15.0 1 / 4
1.14.0 1 / 4
1.13.0 1 / 4
1.12.1 1 / 4
1.12.0 1 / 4
1.11.3 1 / 4
1.11.2 1 / 4
1.11.1 1 / 4
1.11.0 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
1.15.0-canary.44ad4cc2e 1 / 4
1.14.0-canary.891a0c9d4 1 / 4
1.13.0-eap-firestore-pipelines.1.f9c4cdec7 1 / 4
1.13.0-canary.f0b0398eb 1 / 4
1.13.0-canary.e6415ddee 1 / 4
1.13.0-canary.e4b2890fd 1 / 4
1.13.0-canary.d7c311a4b 1 / 4
1.13.0-canary.d4b22a872 1 / 4
1.13.0-canary.cbef6c6e5 1 / 4
1.13.0-canary.a4897a621 1 / 4
1.13.0-canary.9b63cd60e 1 / 4
1.13.0-canary.9101b4611 1 / 4
1.13.0-canary.6abe52967 1 / 4
1.13.0-canary.6ab71fa0b 1 / 4
1.13.0-canary.65a553baf 1 / 4
1.13.0-canary.60d1b18bd 1 / 4
1.13.0-canary.5511b4fa7 1 / 4
1.13.0-canary.44d9891f9 1 / 4
1.13.0-canary.35b284af4 1 / 4
1.13.0-canary.2e7432986 1 / 4
1.13.0-canary.2bd48a604 1 / 4
1.13.0-canary.22e0a1adb 1 / 4
1.13.0-canary.0ffcb26af 1 / 4
1.12.1-canary.f18b25f73 1 / 4
1.12.1-canary.f11b55294 1 / 4
1.12.1-canary.cb19688bf 1 / 4
1.12.1-canary.a9be6757f 1 / 4
1.12.1-canary.9771bffad 1 / 4
1.12.1-canary.5200f7bb7 1 / 4
1.12.1-20250626140224 1 / 4
1.12.0-firebase-studio-sdk-integration.0d857eae1 1 / 4
1.12.0-canary.e59cd7da1 1 / 4
1.12.0-canary.d590889d6 1 / 4
1.12.0-canary.c0617a341 1 / 4
1.12.0-canary.bb57947c9 1 / 4
1.12.0-canary.ae976d029 1 / 4
1.12.0-canary.8072572f9 1 / 4
1.12.0-canary.770e455a6 1 / 4
1.12.0-canary.6cc9a0732 1 / 4
1.12.0-canary.6ab4e13a1 1 / 4
1.12.0-canary.5871fd656 1 / 4
1.12.0-canary.40be2dbb8 1 / 4
1.12.0-canary.2fe754727 1 / 4
1.12.0-canary.230692087 1 / 4
1.12.0-canary.13e6cce88 1 / 4
1.11.2-20250513212531 1 / 4
1.11.1-canary.f8334eade 1 / 4
1.11.1-canary.799de5997 1 / 4
1.11.1-20250507151459 1 / 4
1.11.1-20250505162014 1 / 4
1.11.0-firebase-studio-sdk-integration.9de25069c 1 / 4
1.11.0-firebase-studio-sdk-integration.927daddb8 1 / 4
1.11.0-firebase-studio-sdk-integration.226be0bb1 1 / 4
1.11.0-firebase-studio-sdk-integration.1adc0ae1f 1 / 4
1.11.0-eap-vertexai-hybgoog.31261ca31 1 / 4
Showing 100 of 108 Next page →

v1.15.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.1

1 finding
INFO No provenance attestation provenance

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

v1.11.0

1 finding
INFO No provenance attestation provenance

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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO No provenance attestation provenance

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

INFO No provenance attestation provenance

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

INFO No provenance attestation provenance

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

INFO No provenance attestation provenance

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

INFO No provenance attestation provenance

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

INFO No provenance attestation provenance

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