@firebase/storage-compat

The Firebase Firestore compatibility package

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
dependencies	unvetted-dep:@firebase/util	AI (dependencies): First-party Google Firebase package from the same official monorepo; unvetted status is a pipeline artifact, not a security concern for this package.	ai	2026/04/22
dependencies	unvetted-dep:@firebase/storage	AI (dependencies): First-party Google Firebase package from the same official monorepo; unvetted status is a pipeline artifact, not a security concern for this package.	ai	2026/04/22
dependencies	unvetted-dep:@firebase/storage-types	AI (dependencies): First-party Google Firebase package from the same official monorepo; unvetted status is a pipeline artifact, not a security concern for this package.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): feiyang.chen is an established Firebase/Google publisher (2779 days, 1044 approved packages). Publisher changes within the Firebase SDK team are expected for this monorepo package.	ai	2026/04/22
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a standard TypeScript runtime helper declared in dependencies; phantom detection is a false positive for compiled TS packages.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): Missing README/repo/keywords are typical for @firebase/* scoped sub-packages in a monorepo; not indicative of spam or malicious intent.	ai	2026/04/22

Versions (showing 51 of 54)

Show 232 prereleases View all versions

Version	Deps	Published
0.4.3	5 / 6	2026-05-07
0.4.2	5 / 6	2026-03-19
0.4.1	5 / 6	2026-02-27
0.4.0	5 / 6	2025-07-17
0.3.24	5 / 6	2025-06-30
0.3.23	5 / 6	2025-06-10
0.3.22	5 / 6	2025-05-22
0.3.21	5 / 6	2025-05-20
0.3.20	5 / 6	2025-05-14
0.3.19	5 / 6	2025-05-14
0.3.18	5 / 6	2025-05-07
0.3.17	5 / 6	2025-02-27
0.3.16	5 / 6	2025-02-06
0.3.15	5 / 6	2025-01-16
0.3.14	5 / 6	2024-11-14
0.3.13	5 / 6	2024-10-21
0.3.12	5 / 6	2024-09-18
0.3.11	5 / 6	2024-08-29
0.3.10	5 / 6	2024-08-15
0.3.9	5 / 6	2024-07-03
0.3.8	5 / 6	2024-05-13
0.3.7	5 / 6	2024-04-11
0.3.6	5 / 6	2024-03-28
0.3.5	5 / 6	2024-02-28
0.3.4	5 / 6	2024-02-01
0.3.3	5 / 6	2023-11-27
0.3.2	5 / 6	2023-03-02
0.3.1	5 / 6	2023-02-03
0.3.0	5 / 6	2023-02-02
0.2.1	5 / 6	2023-01-19
0.2.0	5 / 6	2022-12-08
0.1.22	5 / 6	2022-11-10
0.1.21	5 / 6	2022-10-27
0.1.20	5 / 6	2022-10-12
0.1.19	5 / 6	2022-10-11
0.1.18	5 / 6	2022-10-06
0.1.17	5 / 6	2022-07-07
0.1.16	5 / 6	2022-06-23
0.1.15	5 / 6	2022-06-09
0.1.14	5 / 6	2022-05-06
0.1.13	5 / 6	2022-04-14
0.1.12	5 / 6	2022-03-24
0.1.11	5 / 6	2022-03-17
0.1.10	5 / 6	2022-01-27
0.1.9	5 / 6	2022-01-07
0.1.8	5 / 6	2021-11-19
0.1.7	5 / 6	2021-11-11
0.1.6	5 / 6	2021-11-08
0.1.5	5 / 6	2021-11-04
0.1.4	5 / 6	2021-10-14
0.1.3	5 / 6	2021-09-24

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.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.4.1

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.4.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.

v0.3.24

1 finding

LOW No provenance attestation provenance

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

v0.3.23

1 finding

LOW No provenance attestation provenance

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

v0.3.22

1 finding

LOW No provenance attestation provenance

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

v0.3.21

1 finding

LOW No provenance attestation provenance

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

v0.3.20

1 finding

LOW No provenance attestation provenance

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

v0.3.19

1 finding

LOW No provenance attestation provenance

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

v0.3.18

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.3.17

1 finding

LOW No provenance attestation provenance

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

v0.3.16

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.3.15

1 finding

LOW No provenance attestation provenance

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

v0.3.14

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

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

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

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.3.8

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

1 finding

LOW No provenance attestation provenance

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

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

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 2023-03-02) provenance

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

1 finding

LOW No provenance attestation provenance

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

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.1

1 finding

LOW No provenance attestation provenance

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

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.22

1 finding

LOW No provenance attestation provenance

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

v0.1.21

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.1.20

1 finding

LOW No provenance attestation provenance

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

v0.1.19

1 finding

LOW No provenance attestation provenance

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

v0.1.18

1 finding

LOW No provenance attestation provenance

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

v0.1.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 → google-wombot (on 2022-07-07) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.1.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: feiyang.chen → google-wombot (on 2022-06-09) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.1.13

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 2022-04-14) provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

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 2022-01-27) provenance

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

v0.1.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: feiyang.chen → chholland (on 2022-01-07) provenance

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

v0.1.8

2 findings

HIGH Publisher changed: chholland → feiyang.chen (on 2021-11-19) provenance

This version was published by a different npm account than previous versions on 2021-11-19. 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.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

2 findings

HIGH Publisher changed: chholland → feiyang.chen (on 2021-11-08) provenance

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.

LOW No provenance attestation provenance

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

v0.1.5

2 findings

HIGH Publisher changed: chholland → feiyang.chen (on 2021-11-04) provenance

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.

LOW No provenance attestation provenance

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

v0.1.4

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

2 findings

HIGH Publisher changed: chholland → feiyang.chen (on 2021-09-24) provenance

This version was published by a different npm account than previous versions on 2021-09-24. 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.