← Home

@firebase/auth-interop-types

@firebase/auth interop Types

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

Hide prereleases
Version Deps Published
0.2.5 0 / 1
0.2.4 0 / 1
0.2.3 0 / 1
0.2.2 0 / 1
0.2.1 0 / 1
0.2.0 0 / 1
0.1.7 0 / 1
0.1.6 0 / 1
0.1.5 0 / 1
0.1.4 0 / 1
0.1.3 0 / 1
0.1.2 0 / 1
0.1.1 0 / 1
0.1.0 0 / 1
0.2.4-ssl-check.4f23f3343 0 / 1
0.2.4-firebase-studio-sdk-integration.fe1264c00 0 / 1
0.2.4-firebase-studio-sdk-integration.f7536090e 0 / 1
0.2.4-firebase-studio-sdk-integration.dd7924e1b 0 / 1
0.2.4-firebase-studio-sdk-integration.dbac496fa 0 / 1
0.2.4-firebase-studio-sdk-integration.d15eeea26 0 / 1
0.2.4-firebase-studio-sdk-integration.bffdabd70 0 / 1
0.2.4-firebase-studio-sdk-integration.a528caf5f 0 / 1
0.2.4-firebase-studio-sdk-integration.9de25069c 0 / 1
0.2.4-firebase-studio-sdk-integration.927daddb8 0 / 1
0.2.4-firebase-studio-sdk-integration.556d1bed2 0 / 1
0.2.4-firebase-studio-sdk-integration.33b86206f 0 / 1
0.2.4-firebase-studio-sdk-integration.226be0bb1 0 / 1
0.2.4-firebase-studio-sdk-integration.1adc0ae1f 0 / 1
0.2.4-firebase-studio-sdk-integration.12759bc2e 0 / 1
0.2.4-firebase-studio-sdk-integration.11d58925e 0 / 1
0.2.4-firebase-studio-sdk-integration.0d857eae1 0 / 1
0.2.4-firebase-studio-sdk-integration.0615f555a 0 / 1
0.2.4-eap-vertexai-hybridinference.e83974308 0 / 1
0.2.4-eap-vertexai-hybridinference.5fa83b371 0 / 1
0.2.4-eap-vertexai-hybridinference.43a69d5da 0 / 1
0.2.4-eap-vertexai-hybgoog.dc3794a2b 0 / 1
0.2.4-eap-vertexai-hybgoog.abf0491ae 0 / 1
0.2.4-eap-vertexai-hybgoog.31261ca31 0 / 1
0.2.4-eap-firestore-pipelines.2.e4cdd2e06 0 / 1
0.2.4-eap-firestore-pipelines.1.f9c4cdec7 0 / 1
0.2.4-eap-ai-hybridinference.c16cbf1a3 0 / 1
0.2.4-eap-ai-hybridinference.58d92df33 0 / 1
0.2.4-canary.f9aaeca46 0 / 1
0.2.4-canary.f9254b6d2 0 / 1
0.2.4-canary.f92069a21 0 / 1
0.2.4-canary.f8334eade 0 / 1
0.2.4-canary.f73e08b21 0 / 1
0.2.4-canary.f5fc6bf76 0 / 1
0.2.4-canary.f4e0086e3 0 / 1
0.2.4-canary.f2ecae7df 0 / 1
0.2.4-canary.f18b25f73 0 / 1
0.2.4-canary.f11b55294 0 / 1
0.2.4-canary.f0b0398eb 0 / 1
0.2.4-canary.f06cbf99b 0 / 1
0.2.4-canary.efc0117ae 0 / 1
0.2.4-canary.ec91a8611 0 / 1
0.2.4-canary.ec5f37403 0 / 1
0.2.4-canary.ea8512812 0 / 1
0.2.4-canary.ea1f9139e 0 / 1
0.2.4-canary.e99683b17 0 / 1
0.2.4-canary.e6415ddee 0 / 1
0.2.4-canary.e59cd7da1 0 / 1
0.2.4-canary.e4b2890fd 0 / 1
0.2.4-canary.e25317f9f 0 / 1
0.2.4-canary.dd6a8f076 0 / 1
0.2.4-canary.d91169f06 0 / 1
0.2.4-canary.d818df4e8 0 / 1
0.2.4-canary.d7c311a4b 0 / 1
0.2.4-canary.d7b182645 0 / 1
0.2.4-canary.d5ff5a4b1 0 / 1
0.2.4-canary.d5e5795c9 0 / 1
0.2.4-canary.d590889d6 0 / 1
0.2.4-canary.d5428f3d2 0 / 1
0.2.4-canary.d5082f9f2 0 / 1
0.2.4-canary.d4b22a872 0 / 1
0.2.4-canary.d1d898f55 0 / 1
0.2.4-canary.ccbf7ba36 0 / 1
0.2.4-canary.cc605e728 0 / 1
0.2.4-canary.cbef6c6e5 0 / 1
0.2.4-canary.cb3bdd812 0 / 1
0.2.4-canary.cb19688bf 0 / 1
0.2.4-canary.c8263c471 0 / 1
0.2.4-canary.c5f08a9bc 0 / 1
0.2.4-canary.c4a3a5643 0 / 1
0.2.4-canary.c48b47674 0 / 1
0.2.4-canary.c47bd7175 0 / 1
0.2.4-canary.c1237662e 0 / 1
0.2.4-canary.c0617a341 0 / 1
0.2.4-canary.bfb9accdc 0 / 1
0.2.4-canary.bc5a7c4a7 0 / 1
0.2.4-canary.bc2b2cdea 0 / 1
0.2.4-canary.bb57947c9 0 / 1
0.2.4-canary.ba0bc39bb 0 / 1
0.2.4-canary.b97eab36a 0 / 1
0.2.4-canary.b9209dc91 0 / 1
0.2.4-canary.b7e18d0ff 0 / 1
0.2.4-canary.b5df4ae71 0 / 1
0.2.4-canary.b2827448b 0 / 1
0.2.4-canary.b228a2ab9 0 / 1
0.2.4-canary.b10a296fa 0 / 1
Showing 100 of 229 Next page →

v0.2.5

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

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. 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. Consider requesting the maintainer enable provenance via CI/CD.