@firebase/functions-types Apache-2.0 34 versions

@firebase/functions-types

npm Repository Homepage

@firebase/functions Types

34

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.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): google-wombot is Firebase's official publishing bot; publisher change from firebase-ops to google-wombot is a documented Firebase pipeline migration, not a compromise.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers (chholland, feiyang.chen, google-wombot) are part of the Firebase/Google team transition; consistent with legitimate org-level change.	ai	2026/04/22
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers reflect Firebase team rotation, not a hostile takeover. Publisher is the official Firebase bot account.	ai	2026/04/22
publish-pattern	dormant-publish	AI (publish-pattern): Types-only package; long dormancy is expected when the API surface is stable. Published by official Firebase bot, not a suspicious actor.	ai	2026/04/22

Versions (showing 34 of 34)

Show 215 prereleases

Version	Deps	Published
0.6.4	0 / 1	2026-05-07
0.6.3	0 / 1	2024-11-14
0.6.2	0 / 1	2024-05-13
0.6.1	0 / 1	2024-03-28
0.6.0	0 / 1	2022-12-08
0.5.1	0 / 1	2022-10-27
0.5.0	0 / 1	2021-08-25
0.4.0	0 / 1	2020-10-26
0.3.17	0 / 1	2020-05-21
0.3.16	0 / 1	2020-03-13
0.3.15	0 / 1	2020-02-28
0.3.14	0 / 1	2020-02-06
0.3.13	0 / 1	2019-12-12
0.3.12	0 / 1	2019-12-06
0.3.11	0 / 1	2019-11-21
0.3.10	0 / 1	2019-10-16
0.3.9	0 / 1	2019-10-10
0.3.8	0 / 1	2019-07-25
0.3.7	0 / 1	2019-07-19
0.3.6	0 / 1	2019-06-20
0.3.5	0 / 1	2019-04-30
0.3.4	0 / 1	2019-04-18
0.3.3	0 / 1	2019-04-11
0.3.2	0 / 1	2019-03-21
0.3.1	0 / 1	2019-03-14
0.3.0	0 / 1	2019-03-02
0.2.3	0 / 1	2019-02-14
0.2.2	0 / 1	2019-01-24
0.2.1	0 / 1	2018-11-08
0.2.0	0 / 1	2018-06-28
0.1.3	0 / 1	2018-05-24
0.1.2	0 / 1	2018-05-10
0.1.1	0 / 0	2018-04-19
0.1.0	0 / 1	2018-03-20

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

2 findings

HIGH Publisher changed: firebase-ops → google-wombot (on 2024-11-14) provenance

This version was published by a different npm account than previous versions on 2024-11-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → google-wombot (on 2022-12-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-12-08. This could indicate a legitimate maintainer transition or an account compromise.

v0.5.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → google-wombot (on 2022-10-27) provenance

[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.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2021-08-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-25. This could indicate a legitimate maintainer transition or an account compromise.

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.17

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2020-05-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-21. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.16

1 finding

LOW No provenance attestation provenance

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

v0.3.15

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2020-02-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-02-28. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.14

1 finding

LOW No provenance attestation provenance

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

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-12-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-12-06. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.11

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-11-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-21. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-10-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-10. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2019-07-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-07-25. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2019-06-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-20. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2019-03-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-14. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2019-02-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-14. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → feiyang.chen (on 2018-11-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-08. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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