← Home

@firebase/functions-compat

npm Repository Homepage
100
Versions
Apache-2.0
License
No
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
dependencies unvetted-dep:@firebase/util AI (dependencies): @firebase/util is a sibling Firebase SDK package from the same Google/Firebase publisher; unvetted status is a pipeline artifact, not a real risk for this package. ai
dependencies unvetted-dep:@firebase/functions AI (dependencies): @firebase/functions is the core sibling package this compat wrapper depends on; same publisher/monorepo, not a real risk. ai
provenance publisher-changed AI (provenance): chholland is a long-standing Firebase/Google publisher (2677 days, 1138 approved packages). Publisher rotation within the Firebase team is expected and not indicative of compromise. ai
npm-metadata no-description AI (npm-metadata): Firebase monorepo sub-packages commonly omit descriptions; this is a known pattern for @firebase/* compat packages, not a malware indicator. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard TypeScript runtime helper dependency used by all Firebase SDK packages; its implicit usage is expected and benign. ai
provenance no-provenance AI (provenance): Google/Firebase publishes via google-wombot without Sigstore provenance; this is consistent across all @firebase/* packages and not a risk signal. ai

Versions (showing 100 of 287)

Hide prereleases
Version Deps Published
0.4.5 5 / 5
0.4.4 5 / 5
0.4.3 5 / 5
0.4.2 5 / 5
0.4.1 5 / 5
0.4.0 5 / 5
0.3.26 5 / 5
0.3.25 5 / 5
0.3.24 5 / 5
0.3.23 5 / 5
0.3.22 5 / 5
0.3.21 5 / 5
0.3.20 5 / 5
0.3.19 5 / 5
0.3.18 5 / 5
0.3.17 5 / 5
0.3.16 5 / 5
0.3.15 5 / 5
0.3.14 5 / 5
0.3.13 5 / 5
0.3.12 5 / 5
0.3.11 5 / 5
0.3.10 5 / 5
0.3.9 5 / 5
0.3.8 5 / 5
0.3.7 5 / 5
0.3.6 5 / 5
0.3.5 5 / 5
0.3.4 5 / 5
0.3.3 5 / 5
0.3.2 5 / 5
0.3.1 5 / 5
0.3.0 5 / 5
0.2.8 5 / 5
0.2.7 5 / 5
0.2.6 5 / 5
0.2.5 5 / 5
0.2.4 5 / 5
0.2.3 5 / 5
0.2.2 5 / 5
0.2.1 5 / 5
0.2.0 5 / 5
0.1.12 5 / 5
0.1.11 5 / 5
0.1.10 5 / 5
0.1.9 5 / 5
0.1.8 5 / 5
0.1.7 5 / 5
0.1.6 5 / 5
0.1.5 5 / 5
0.1.4 5 / 5
0.1.3 5 / 5
0.1.2 5 / 5
0.1.1 5 / 5
0.1.0 5 / 5
0.4.3-canary.f4e0086e3 5 / 5
0.4.3-canary.bfb9accdc 5 / 5
0.4.3-canary.ba0bc39bb 5 / 5
0.4.3-canary.742e17a8e 5 / 5
0.4.3-canary.44ad4cc2e 5 / 5
0.4.3-20260317152345 5 / 5
0.4.2-canary.d7b182645 5 / 5
0.4.2-canary.891a0c9d4 5 / 5
0.4.2-canary.843a8d789 5 / 5
0.4.2-canary.792c61671 5 / 5
0.4.2-canary.78384d32c 5 / 5
0.4.2-canary.22476e1bc 5 / 5
0.4.2-20260224183151 5 / 5
0.4.1-eap-firestore-pipelines.2.e4cdd2e06 5 / 5
0.4.1-eap-firestore-pipelines.1.f9c4cdec7 5 / 5
0.4.1-canary.f9aaeca46 5 / 5
0.4.1-canary.f9254b6d2 5 / 5
0.4.1-canary.f5fc6bf76 5 / 5
0.4.1-canary.f2ecae7df 5 / 5
0.4.1-canary.f0b0398eb 5 / 5
0.4.1-canary.f06cbf99b 5 / 5
0.4.1-canary.efc0117ae 5 / 5
0.4.1-canary.ea8512812 5 / 5
0.4.1-canary.e6415ddee 5 / 5
0.4.1-canary.e4b2890fd 5 / 5
0.4.1-canary.d818df4e8 5 / 5
0.4.1-canary.d7c311a4b 5 / 5
0.4.1-canary.d5ff5a4b1 5 / 5
0.4.1-canary.d4b22a872 5 / 5
0.4.1-canary.d1d898f55 5 / 5
0.4.1-canary.ccbf7ba36 5 / 5
0.4.1-canary.cb3bdd812 5 / 5
0.4.1-canary.c8263c471 5 / 5
0.4.1-canary.c4a3a5643 5 / 5
0.4.1-canary.c48b47674 5 / 5
0.4.1-canary.c47bd7175 5 / 5
0.4.1-canary.c1237662e 5 / 5
0.4.1-canary.bc5a7c4a7 5 / 5
0.4.1-canary.bc2b2cdea 5 / 5
0.4.1-canary.b7e18d0ff 5 / 5
0.4.1-canary.b2827448b 5 / 5
0.4.1-canary.b228a2ab9 5 / 5
0.4.1-canary.b10a296fa 5 / 5
0.4.1-canary.a4848b401 5 / 5
0.4.1-canary.a09ef786f 5 / 5
Showing 100 of 287 Next page →

v0.4.5

1 finding
INFO No provenance attestation provenance

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

v0.4.4

1 finding
INFO No provenance attestation provenance

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

v0.4.3-canary.f4e0086e3

1 finding
INFO No provenance attestation provenance

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

v0.4.3-canary.bfb9accdc

1 finding
INFO No provenance attestation provenance

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

v0.4.3-canary.ba0bc39bb

1 finding
INFO No provenance attestation provenance

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

v0.4.3-canary.742e17a8e

1 finding
INFO No provenance attestation provenance

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

v0.4.3-canary.44ad4cc2e

1 finding
INFO No provenance attestation provenance

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

v0.4.3-20260317152345

1 finding
INFO No provenance attestation provenance

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

v0.4.2-canary.d7b182645

1 finding
INFO No provenance attestation provenance

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

v0.4.2-canary.891a0c9d4

1 finding
INFO No provenance attestation provenance

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

v0.4.2-canary.843a8d789

1 finding
INFO No provenance attestation provenance

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

v0.4.2-canary.792c61671

1 finding
INFO No provenance attestation provenance

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

v0.4.2-canary.78384d32c

1 finding
INFO No provenance attestation provenance

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

v0.4.2-canary.22476e1bc

1 finding
INFO No provenance attestation provenance

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

v0.4.2-20260224183151

1 finding
INFO No provenance attestation provenance

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

v0.4.1-eap-firestore-pipelines.2.e4cdd2e06

1 finding
INFO No provenance attestation provenance

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

v0.4.1-eap-firestore-pipelines.1.f9c4cdec7

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.

v0.4.1-canary.f9aaeca46

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.f9254b6d2

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.f5fc6bf76

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.f2ecae7df

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.

v0.4.1-canary.f0b0398eb

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.f06cbf99b

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.efc0117ae

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.ea8512812

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.

v0.4.1-canary.e6415ddee

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.e4b2890fd

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.d818df4e8

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.d7c311a4b

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.d5ff5a4b1

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.d4b22a872

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.d1d898f55

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.ccbf7ba36

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.

v0.4.1-canary.cb3bdd812

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.

v0.4.1-canary.c8263c471

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.

v0.4.1-canary.c4a3a5643

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.c48b47674

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.c47bd7175

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.

v0.4.1-canary.c1237662e

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.

v0.4.1-canary.bc5a7c4a7

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.

v0.4.1-canary.bc2b2cdea

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.b7e18d0ff

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.

v0.4.1-canary.b2827448b

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.b228a2ab9

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.b10a296fa

1 finding
INFO No provenance attestation provenance

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

v0.4.1-canary.a4848b401

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.

v0.4.1-canary.a09ef786f

1 finding
INFO No provenance attestation provenance

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