@firebase/functions
This is the Firebase Functions 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Firebase SDK undergoes routine team transitions; removal of prior maintainers alongside addition of Google Firebase team members is expected for this official Google package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): feiyang.chen and hiranya911 are established Firebase team members; maintainer additions reflect legitimate Firebase SDK team changes. | ai | |
| provenance | publisher-changed | AI (provenance): feiyang.chen is a known Firebase/Google team member with 49 published packages and long history; the 2018 publisher transition is a documented Firebase team change, not a compromise. | ai | |
| phantom-deps | phantom-dep:@firebase/messaging-types | AI (phantom-deps): Same @firebase org scope; used for type declarations in Firebase SDK monorepo packages, not a runtime import. Common pattern across Firebase packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): undici is a legitimate, widely-used HTTP client replacing node-fetch; not a suspicious dependency injection pattern. | ai | |
| provenance | no-provenance | AI (provenance): Google-published Firebase SDK; provenance attestation is a future-state improvement, not a security defect for established publishers. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long gaps between Firebase SDK releases are normal for monorepo cadence; publisher's 2589-day history and 3133 approved packages rule out account takeover. | ai | |
| dependencies | unvetted-dep:undici | AI (dependencies): undici 5.28.4 is Node.js's official HTTP client; widely used and maintained. Replacement for node-fetch is a standard modernization pattern. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper declared as a dependency; its use as an implicit runtime dep is a well-known pattern for TypeScript-compiled packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive for scoped Firebase package; documentation is in monorepo, not individual package README. | ai |
Versions (showing 51 of 139)
| Version | Deps | Published |
|---|---|---|
| 0.13.4 | 6 / 5 | |
| 0.13.3 | 6 / 5 | |
| 0.13.2 | 6 / 5 | |
| 0.13.1 | 6 / 5 | |
| 0.13.0 | 6 / 5 | |
| 0.12.9 | 6 / 5 | |
| 0.12.8 | 6 / 5 | |
| 0.12.7 | 6 / 5 | |
| 0.12.6 | 6 / 5 | |
| 0.12.5 | 6 / 5 | |
| 0.12.4 | 6 / 5 | |
| 0.12.3 | 6 / 5 | |
| 0.12.2 | 6 / 5 | |
| 0.12.1 | 6 / 5 | |
| 0.12.0 | 6 / 5 | |
| 0.11.10 | 6 / 5 | |
| 0.11.9 | 6 / 5 | |
| 0.11.8 | 7 / 5 | |
| 0.11.7 | 7 / 5 | |
| 0.11.6 | 7 / 5 | |
| 0.11.5 | 7 / 5 | |
| 0.11.4 | 7 / 5 | |
| 0.11.3 | 7 / 5 | |
| 0.11.2 | 7 / 5 | |
| 0.11.1 | 7 / 5 | |
| 0.11.0 | 7 / 5 | |
| 0.10.0 | 7 / 5 | |
| 0.9.4 | 7 / 5 | |
| 0.9.3 | 7 / 5 | |
| 0.9.2 | 7 / 5 | |
| 0.9.1 | 7 / 5 | |
| 0.9.0 | 7 / 5 | |
| 0.8.8 | 7 / 5 | |
| 0.8.7 | 7 / 5 | |
| 0.8.6 | 7 / 5 | |
| 0.8.5 | 7 / 5 | |
| 0.8.4 | 7 / 5 | |
| 0.8.3 | 7 / 5 | |
| 0.8.2 | 7 / 5 | |
| 0.8.1 | 7 / 5 | |
| 0.8.0 | 7 / 5 | |
| 0.7.11 | 7 / 5 | |
| 0.7.10 | 7 / 5 | |
| 0.7.9 | 7 / 5 | |
| 0.7.8 | 7 / 5 | |
| 0.7.7 | 7 / 5 | |
| 0.7.6 | 7 / 5 | |
| 0.7.5 | 7 / 5 | |
| 0.7.4 | 7 / 5 | |
| 0.7.3 | 7 / 5 | |
| 0.7.2 | 7 / 5 |
v0.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.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.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.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-10-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.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 2022-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.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-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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 2021-11-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.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 2021-11-08. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.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 2021-11-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.