@firebase/functions-compat
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 |
|---|---|---|---|---|
| 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 87 of 287)
v0.3.25-canary.6cc9a0732
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.24-canary.35ad52663
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.22-20250513212531
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.21-canary.f92069a21
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.21-canary.51e7b489d
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.