← Home

@firebase/app-types

npm Repository Homepage

@firebase/app 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
dependencies unvetted-dep:@firebase/logger AI (dependencies): @firebase/logger is an official Firebase SDK package published by the same Google/Firebase publisher ecosystem; its inclusion as a dependency is expected and benign for this package. ai
provenance publisher-changed AI (provenance): Publisher change reflects a legitimate Firebase/Google team transition; chholland is a well-established publisher with a long track record and many approved packages. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (chholland, feiyang.chen, google-wombot, hiranya911) are consistent with Firebase SDK team members and Google automation; legitimate team rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of prior maintainers is consistent with the documented Firebase team transition; no malicious indicators present. ai
bogus-package bogus-package AI (bogus-package): Types-only package from Google's Firebase SDK monorepo; short README and no keywords are expected for internal type definition packages, not spam indicators. ai
provenance no-provenance AI (provenance): Published by Google's official Firebase bot; lack of Sigstore provenance is acceptable given the publisher's established identity and ecosystem trust. ai

Versions (showing 100 of 260)

Hide prereleases
Version Deps Published
0.9.5 1 / 1
0.9.4 1 / 1
0.9.3 0 / 1
0.9.2 0 / 1
0.9.1 0 / 1
0.9.0 0 / 1
0.8.1 0 / 1
0.8.0 0 / 1
0.7.0 0 / 1
0.6.3 0 / 1
0.6.2 0 / 1
0.6.1 0 / 1
0.6.0 0 / 1
0.5.3 0 / 1
0.5.2 0 / 1
0.5.1 0 / 1
0.5.0 0 / 1
0.4.9 0 / 1
0.4.8 0 / 1
0.4.7 0 / 1
0.4.6 0 / 1
0.4.5 0 / 1
0.4.4 0 / 1
0.4.3 0 / 1
0.4.2 0 / 1
0.4.1 0 / 1
0.4.0 0 / 1
0.3.10 0 / 1
0.3.9 0 / 1
0.3.8 0 / 1
0.3.7 0 / 1
0.3.6 0 / 1
0.3.5 0 / 1
0.3.4 0 / 1
0.3.3 0 / 1
0.3.2 0 / 1
0.3.1 0 / 1
0.3.0 0 / 0
0.2.0 0 / 0
0.1.2 0 / 1
0.1.1 0 / 1
0.1.0 0 / 1
0.9.4-20260409172004 1 / 1
0.9.4-20260408221811 1 / 1
0.9.4-20260408201731 1 / 1
0.9.3-ssl-check.4f23f3343 0 / 1
0.9.3-firebase-studio-sdk-integration.fe1264c00 0 / 1
0.9.3-firebase-studio-sdk-integration.f7536090e 0 / 1
0.9.3-firebase-studio-sdk-integration.dd7924e1b 0 / 1
0.9.3-firebase-studio-sdk-integration.dbac496fa 0 / 1
0.9.3-firebase-studio-sdk-integration.d15eeea26 0 / 1
0.9.3-firebase-studio-sdk-integration.bffdabd70 0 / 1
0.9.3-firebase-studio-sdk-integration.a528caf5f 0 / 1
0.9.3-firebase-studio-sdk-integration.9de25069c 0 / 1
0.9.3-firebase-studio-sdk-integration.927daddb8 0 / 1
0.9.3-firebase-studio-sdk-integration.556d1bed2 0 / 1
0.9.3-firebase-studio-sdk-integration.33b86206f 0 / 1
0.9.3-firebase-studio-sdk-integration.226be0bb1 0 / 1
0.9.3-firebase-studio-sdk-integration.1adc0ae1f 0 / 1
0.9.3-firebase-studio-sdk-integration.12759bc2e 0 / 1
0.9.3-firebase-studio-sdk-integration.11d58925e 0 / 1
0.9.3-firebase-studio-sdk-integration.0d857eae1 0 / 1
0.9.3-firebase-studio-sdk-integration.0615f555a 0 / 1
0.9.3-eap-vertexai-hybridinference.e83974308 0 / 1
0.9.3-eap-vertexai-hybridinference.5fa83b371 0 / 1
0.9.3-eap-vertexai-hybridinference.43a69d5da 0 / 1
0.9.3-eap-vertexai-hybgoog.dc3794a2b 0 / 1
0.9.3-eap-vertexai-hybgoog.abf0491ae 0 / 1
0.9.3-eap-vertexai-hybgoog.31261ca31 0 / 1
0.9.3-eap-firestore-pipelines.2.e4cdd2e06 0 / 1
0.9.3-eap-firestore-pipelines.1.f9c4cdec7 0 / 1
0.9.3-eap-ai-hybridinference.c16cbf1a3 0 / 1
0.9.3-eap-ai-hybridinference.58d92df33 0 / 1
0.9.3-canary.f9aaeca46 0 / 1
0.9.3-canary.f9254b6d2 0 / 1
0.9.3-canary.f92069a21 0 / 1
0.9.3-canary.f8334eade 0 / 1
0.9.3-canary.f73e08b21 0 / 1
0.9.3-canary.f5fc6bf76 0 / 1
0.9.3-canary.f4e0086e3 0 / 1
0.9.3-canary.f2ecae7df 0 / 1
0.9.3-canary.f18b25f73 0 / 1
0.9.3-canary.f11b55294 0 / 1
0.9.3-canary.f0b0398eb 0 / 1
0.9.3-canary.f06cbf99b 0 / 1
0.9.3-canary.efc0117ae 0 / 1
0.9.3-canary.ec91a8611 0 / 1
0.9.3-canary.ec5f37403 0 / 1
0.9.3-canary.ea8512812 0 / 1
0.9.3-canary.ea1f9139e 0 / 1
0.9.3-canary.e99683b17 0 / 1
0.9.3-canary.e6415ddee 0 / 1
0.9.3-canary.e59cd7da1 0 / 1
0.9.3-canary.e4b2890fd 0 / 1
0.9.3-canary.e25317f9f 0 / 1
0.9.3-canary.dd6a8f076 0 / 1
0.9.3-canary.d91169f06 0 / 1
0.9.3-canary.d818df4e8 0 / 1
0.9.3-canary.d7c311a4b 0 / 1
0.9.3-canary.d7b182645 0 / 1
Showing 100 of 260 Next page →

v0.9.5

1 finding
INFO No provenance attestation provenance

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

v0.9.4-20260409172004

1 finding
INFO No provenance attestation provenance

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

v0.9.4-20260408221811

1 finding
INFO No provenance attestation provenance

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

v0.9.4-20260408201731

1 finding
INFO No provenance attestation provenance

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

v0.9.3-ssl-check.4f23f3343

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.fe1264c00

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.f7536090e

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.dd7924e1b

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.dbac496fa

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.d15eeea26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.bffdabd70

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.a528caf5f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.9de25069c

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.927daddb8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.556d1bed2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.33b86206f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.226be0bb1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.1adc0ae1f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.12759bc2e

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.11d58925e

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.0d857eae1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-firebase-studio-sdk-integration.0615f555a

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-vertexai-hybridinference.e83974308

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-vertexai-hybridinference.5fa83b371

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-vertexai-hybridinference.43a69d5da

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-vertexai-hybgoog.dc3794a2b

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-vertexai-hybgoog.abf0491ae

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-vertexai-hybgoog.31261ca31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-firestore-pipelines.2.e4cdd2e06

1 finding
INFO No provenance attestation provenance

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

v0.9.3-eap-firestore-pipelines.1.f9c4cdec7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-ai-hybridinference.c16cbf1a3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-eap-ai-hybridinference.58d92df33

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.f9aaeca46

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.f9254b6d2

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.f92069a21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.f8334eade

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.f73e08b21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.f5fc6bf76

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.f4e0086e3

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.f2ecae7df

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.f18b25f73

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.f11b55294

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.f0b0398eb

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.f06cbf99b

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.efc0117ae

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.ec91a8611

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.ec5f37403

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.ea8512812

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.ea1f9139e

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.e99683b17

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.e6415ddee

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.e59cd7da1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.e4b2890fd

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.e25317f9f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.dd6a8f076

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.d91169f06

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3-canary.d818df4e8

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.d7c311a4b

1 finding
INFO No provenance attestation provenance

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

v0.9.3-canary.d7b182645

1 finding
INFO No provenance attestation provenance

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