@firebase/storage-compat
The Firebase Firestore compatibility package
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): 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 86 of 286)
v0.3.22-canary.d590889d6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18-eap-ai-hybridinference.c16cbf1a3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17-canary.080a90dcc
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.