@firebase/auth-interop-types
@firebase/auth interop Types
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): This is a types-only package (index.d.ts); tiny payload, minimal README, and no keywords are expected and by design for this package. | ai | |
| provenance | publisher-changed | AI (provenance): google-wombot is Google's official Firebase publishing bot; publisher transitions from individual Google engineers to the bot account are standard practice for this SDK. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer changes within the Firebase/Google org are routine; google-wombot is a known Google automation account with a long track record. | ai |
Versions (showing 100 of 229)
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-ssl-check.4f23f3343
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.
Package 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.
Package 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.
Package 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.
Package 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.
Package 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.
Package 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.
Package 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.
Package 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.
Package 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.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-eap-vertexai-hybgoog.dc3794a2b
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-eap-vertexai-hybgoog.abf0491ae
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-eap-vertexai-hybgoog.31261ca31
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. Consider requesting the maintainer enable provenance via CI/CD.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-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.2.4-eap-ai-hybridinference.58d92df33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.f9aaeca46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.f9254b6d2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.f92069a21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.f8334eade
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.f73e08b21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.f5fc6bf76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.f4e0086e3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.f2ecae7df
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.f18b25f73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.f11b55294
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.f0b0398eb
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.f06cbf99b
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.efc0117ae
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.ec91a8611
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.ec5f37403
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.ea8512812
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.ea1f9139e
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.e99683b17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.e6415ddee
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.e59cd7da1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.e4b2890fd
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.e25317f9f
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.dd6a8f076
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.d91169f06
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.d818df4e8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.d7c311a4b
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.d7b182645
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.d5ff5a4b1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.d5e5795c9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.d590889d6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.d5428f3d2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.d5082f9f2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.d4b22a872
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.d1d898f55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.ccbf7ba36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.cc605e728
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.cbef6c6e5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.cb3bdd812
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.cb19688bf
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.c8263c471
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.c5f08a9bc
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.c4a3a5643
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.c48b47674
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.c47bd7175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.c1237662e
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.c0617a341
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.bfb9accdc
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.bc5a7c4a7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.bc2b2cdea
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.bb57947c9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.ba0bc39bb
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.b97eab36a
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.b9209dc91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.b7e18d0ff
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.b5df4ae71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4-canary.b2827448b
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.b228a2ab9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4-canary.b10a296fa
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.