← Home

@firebase/performance-types

npm Repository Homepage

@firebase/performance 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
provenance publisher-changed AI (provenance): google-wombot is Google's official Firebase SDK automation bot; publisher transitions from firebase-ops to google-wombot are routine and expected across the Firebase JS SDK monorepo. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal is consistent with Firebase SDK team consolidating publishing under the google-wombot automation account; not indicative of a takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Types-only package with stable API; long dormancy is expected. New publish is a minor CI tooling update consistent with Firebase monorepo-wide changes. ai

Versions (showing 100 of 235)

Hide prereleases
Version Deps Published
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.1 0 / 1
0.1.0 0 / 1
0.0.13 0 / 1
0.0.12 0 / 1
0.0.11 0 / 1
0.0.10 0 / 1
0.0.9 0 / 1
0.0.8 0 / 1
0.0.7 0 / 1
0.0.6 0 / 1
0.0.5 0 / 1
0.0.4 0 / 1
0.0.3 0 / 1
0.0.2 0 / 1
0.0.1 0 / 1
0.2.3-ssl-check.4f23f3343 0 / 1
0.2.3-firebase-studio-sdk-integration.fe1264c00 0 / 1
0.2.3-firebase-studio-sdk-integration.f7536090e 0 / 1
0.2.3-firebase-studio-sdk-integration.dd7924e1b 0 / 1
0.2.3-firebase-studio-sdk-integration.dbac496fa 0 / 1
0.2.3-firebase-studio-sdk-integration.d15eeea26 0 / 1
0.2.3-firebase-studio-sdk-integration.bffdabd70 0 / 1
0.2.3-firebase-studio-sdk-integration.a528caf5f 0 / 1
0.2.3-firebase-studio-sdk-integration.9de25069c 0 / 1
0.2.3-firebase-studio-sdk-integration.927daddb8 0 / 1
0.2.3-firebase-studio-sdk-integration.556d1bed2 0 / 1
0.2.3-firebase-studio-sdk-integration.33b86206f 0 / 1
0.2.3-firebase-studio-sdk-integration.226be0bb1 0 / 1
0.2.3-firebase-studio-sdk-integration.1adc0ae1f 0 / 1
0.2.3-firebase-studio-sdk-integration.12759bc2e 0 / 1
0.2.3-firebase-studio-sdk-integration.11d58925e 0 / 1
0.2.3-firebase-studio-sdk-integration.0d857eae1 0 / 1
0.2.3-firebase-studio-sdk-integration.0615f555a 0 / 1
0.2.3-eap-vertexai-hybridinference.e83974308 0 / 1
0.2.3-eap-vertexai-hybridinference.5fa83b371 0 / 1
0.2.3-eap-vertexai-hybridinference.43a69d5da 0 / 1
0.2.3-eap-vertexai-hybgoog.dc3794a2b 0 / 1
0.2.3-eap-vertexai-hybgoog.abf0491ae 0 / 1
0.2.3-eap-vertexai-hybgoog.31261ca31 0 / 1
0.2.3-eap-firestore-pipelines.2.e4cdd2e06 0 / 1
0.2.3-eap-firestore-pipelines.1.f9c4cdec7 0 / 1
0.2.3-eap-ai-hybridinference.c16cbf1a3 0 / 1
0.2.3-eap-ai-hybridinference.58d92df33 0 / 1
0.2.3-canary.f9aaeca46 0 / 1
0.2.3-canary.f9254b6d2 0 / 1
0.2.3-canary.f92069a21 0 / 1
0.2.3-canary.f8334eade 0 / 1
0.2.3-canary.f73e08b21 0 / 1
0.2.3-canary.f5fc6bf76 0 / 1
0.2.3-canary.f4e0086e3 0 / 1
0.2.3-canary.f2ecae7df 0 / 1
0.2.3-canary.f18b25f73 0 / 1
0.2.3-canary.f11b55294 0 / 1
0.2.3-canary.f0b0398eb 0 / 1
0.2.3-canary.f06cbf99b 0 / 1
0.2.3-canary.efc0117ae 0 / 1
0.2.3-canary.ec91a8611 0 / 1
0.2.3-canary.ec5f37403 0 / 1
0.2.3-canary.ea8512812 0 / 1
0.2.3-canary.ea1f9139e 0 / 1
0.2.3-canary.e99683b17 0 / 1
0.2.3-canary.e6415ddee 0 / 1
0.2.3-canary.e59cd7da1 0 / 1
0.2.3-canary.e4b2890fd 0 / 1
0.2.3-canary.e25317f9f 0 / 1
0.2.3-canary.dd6a8f076 0 / 1
0.2.3-canary.d91169f06 0 / 1
0.2.3-canary.d818df4e8 0 / 1
0.2.3-canary.d7c311a4b 0 / 1
0.2.3-canary.d7b182645 0 / 1
0.2.3-canary.d5ff5a4b1 0 / 1
0.2.3-canary.d5e5795c9 0 / 1
0.2.3-canary.d590889d6 0 / 1
0.2.3-canary.d5428f3d2 0 / 1
0.2.3-canary.d5082f9f2 0 / 1
0.2.3-canary.d4b22a872 0 / 1
0.2.3-canary.d1d898f55 0 / 1
0.2.3-canary.ccbf7ba36 0 / 1
0.2.3-canary.cc605e728 0 / 1
0.2.3-canary.cbef6c6e5 0 / 1
0.2.3-canary.cb3bdd812 0 / 1
0.2.3-canary.cb19688bf 0 / 1
0.2.3-canary.c8263c471 0 / 1
0.2.3-canary.c5f08a9bc 0 / 1
0.2.3-canary.c4a3a5643 0 / 1
0.2.3-canary.c48b47674 0 / 1
0.2.3-canary.c47bd7175 0 / 1
0.2.3-canary.c1237662e 0 / 1
0.2.3-canary.c0617a341 0 / 1
0.2.3-canary.bfb9accdc 0 / 1
0.2.3-canary.bc5a7c4a7 0 / 1
0.2.3-canary.bc2b2cdea 0 / 1
0.2.3-canary.bb57947c9 0 / 1
0.2.3-canary.ba0bc39bb 0 / 1
0.2.3-canary.b97eab36a 0 / 1
Showing 100 of 235 Next page →

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3-ssl-check.4f23f3343

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v0.2.3-eap-vertexai-hybridinference.e83974308

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

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

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

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

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

v0.2.3-eap-vertexai-hybgoog.dc3794a2b

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

v0.2.3-eap-vertexai-hybgoog.abf0491ae

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

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

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

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

1 finding
LOW No provenance attestation provenance

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

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

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

v0.2.3-eap-ai-hybridinference.c16cbf1a3

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

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

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

v0.2.3-canary.f9aaeca46

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.f9254b6d2

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.f92069a21

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

v0.2.3-canary.f8334eade

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

v0.2.3-canary.f73e08b21

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

v0.2.3-canary.f5fc6bf76

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.f4e0086e3

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.f2ecae7df

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

v0.2.3-canary.f18b25f73

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

v0.2.3-canary.f11b55294

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

v0.2.3-canary.f0b0398eb

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.f06cbf99b

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.efc0117ae

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.ec91a8611

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

v0.2.3-canary.ec5f37403

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

v0.2.3-canary.ea8512812

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

v0.2.3-canary.ea1f9139e

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

v0.2.3-canary.e99683b17

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

v0.2.3-canary.e6415ddee

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.e59cd7da1

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

v0.2.3-canary.e4b2890fd

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.e25317f9f

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

v0.2.3-canary.dd6a8f076

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

v0.2.3-canary.d91169f06

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

v0.2.3-canary.d818df4e8

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.d7c311a4b

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.d7b182645

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.d5ff5a4b1

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.d5e5795c9

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

v0.2.3-canary.d590889d6

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

v0.2.3-canary.d5428f3d2

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

v0.2.3-canary.d5082f9f2

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

v0.2.3-canary.d4b22a872

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.d1d898f55

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.ccbf7ba36

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

v0.2.3-canary.cc605e728

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

v0.2.3-canary.cbef6c6e5

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

v0.2.3-canary.cb3bdd812

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

v0.2.3-canary.cb19688bf

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

v0.2.3-canary.c8263c471

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

v0.2.3-canary.c5f08a9bc

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

v0.2.3-canary.c4a3a5643

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.c48b47674

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.c47bd7175

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

v0.2.3-canary.c1237662e

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

v0.2.3-canary.c0617a341

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

v0.2.3-canary.bfb9accdc

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.bc5a7c4a7

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

v0.2.3-canary.bc2b2cdea

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.bb57947c9

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

v0.2.3-canary.ba0bc39bb

1 finding
LOW No provenance attestation provenance

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

v0.2.3-canary.b97eab36a

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