← Home

@firebase/storage-compat

The Firebase Firestore compatibility package

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): First-party Google Firebase package from the same official monorepo; unvetted status is a pipeline artifact, not a security concern for this package. ai
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
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
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
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
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

Versions (showing 100 of 286)

Hide prereleases
Version Deps Published
0.4.3 5 / 6
0.4.2 5 / 6
0.4.1 5 / 6
0.4.0 5 / 6
0.3.24 5 / 6
0.3.23 5 / 6
0.3.22 5 / 6
0.3.21 5 / 6
0.3.20 5 / 6
0.3.19 5 / 6
0.3.18 5 / 6
0.3.17 5 / 6
0.3.16 5 / 6
0.3.15 5 / 6
0.3.14 5 / 6
0.3.13 5 / 6
0.3.12 5 / 6
0.3.11 5 / 6
0.3.10 5 / 6
0.3.9 5 / 6
0.3.8 5 / 6
0.3.7 5 / 6
0.3.6 5 / 6
0.3.5 5 / 6
0.3.4 5 / 6
0.3.3 5 / 6
0.3.2 5 / 6
0.3.1 5 / 6
0.3.0 5 / 6
0.2.1 5 / 6
0.2.0 5 / 6
0.1.22 5 / 6
0.1.21 5 / 6
0.1.20 5 / 6
0.1.19 5 / 6
0.1.18 5 / 6
0.1.17 5 / 6
0.1.16 5 / 6
0.1.15 5 / 6
0.1.14 5 / 6
0.1.13 5 / 6
0.1.12 5 / 6
0.1.11 5 / 6
0.1.10 5 / 6
0.1.9 5 / 6
0.1.8 5 / 6
0.1.7 5 / 6
0.1.6 5 / 6
0.1.5 5 / 6
0.1.4 5 / 6
0.1.3 5 / 6
0.1.2 5 / 6
0.1.1 5 / 6
0.1.0 5 / 6
0.4.2-canary.f4e0086e3 5 / 6
0.4.2-canary.bfb9accdc 5 / 6
0.4.2-canary.ba0bc39bb 5 / 6
0.4.2-canary.742e17a8e 5 / 6
0.4.2-canary.44ad4cc2e 5 / 6
0.4.2-20260317152345 5 / 6
0.4.1-canary.d7b182645 5 / 6
0.4.1-canary.891a0c9d4 5 / 6
0.4.1-canary.843a8d789 5 / 6
0.4.1-canary.792c61671 5 / 6
0.4.1-canary.78384d32c 5 / 6
0.4.1-canary.22476e1bc 5 / 6
0.4.1-20260224183151 5 / 6
0.4.0-firebase-studio-sdk-integration.f7536090e 5 / 6
0.4.0-firebase-studio-sdk-integration.556d1bed2 5 / 6
0.4.0-eap-firestore-pipelines.2.e4cdd2e06 5 / 6
0.4.0-eap-firestore-pipelines.1.f9c4cdec7 5 / 6
0.4.0-canary.f9aaeca46 5 / 6
0.4.0-canary.f9254b6d2 5 / 6
0.4.0-canary.f5fc6bf76 5 / 6
0.4.0-canary.f2ecae7df 5 / 6
0.4.0-canary.f0b0398eb 5 / 6
0.4.0-canary.f06cbf99b 5 / 6
0.4.0-canary.efc0117ae 5 / 6
0.4.0-canary.ea8512812 5 / 6
0.4.0-canary.e6415ddee 5 / 6
0.4.0-canary.e4b2890fd 5 / 6
0.4.0-canary.e25317f9f 5 / 6
0.4.0-canary.d818df4e8 5 / 6
0.4.0-canary.d7c311a4b 5 / 6
0.4.0-canary.d5ff5a4b1 5 / 6
0.4.0-canary.d4b22a872 5 / 6
0.4.0-canary.d1d898f55 5 / 6
0.4.0-canary.ccbf7ba36 5 / 6
0.4.0-canary.cc605e728 5 / 6
0.4.0-canary.cbef6c6e5 5 / 6
0.4.0-canary.cb3bdd812 5 / 6
0.4.0-canary.c8263c471 5 / 6
0.4.0-canary.c5f08a9bc 5 / 6
0.4.0-canary.c4a3a5643 5 / 6
0.4.0-canary.c48b47674 5 / 6
0.4.0-canary.c47bd7175 5 / 6
0.4.0-canary.c1237662e 5 / 6
0.4.0-canary.bc5a7c4a7 5 / 6
0.4.0-canary.bc2b2cdea 5 / 6
0.4.0-canary.b9209dc91 5 / 6
Showing 100 of 286 Next page →

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

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.

LOW No provenance attestation provenance

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

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

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.

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.

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.

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.

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

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.

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.

LOW No provenance attestation provenance

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

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.