← Home

@firebase/performance

npm Repository Homepage

Firebase performance for web

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 no-provenance AI (provenance): Firebase SDK packages consistently lack Sigstore provenance; this is a known gap in their publishing pipeline, not a per-version risk signal. ai
provenance publisher-changed AI (provenance): google-wombot is Google's official Firebase SDK automation publisher; publisher transitions to this account are expected and legitimate for @firebase/* packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Firebase SDK maintainer roster changes over time are expected for a long-lived Google project; removal of individual maintainers is not a takeover signal here. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy signal is an artifact of comparing against a very old approved version (v0.2.6); the package has 3087 versions in registry indicating continuous active development. ai
publish-pattern new-deps-added AI (publish-pattern): web-vitals is Google's own Core Web Vitals library; @firebase/component is part of the Firebase SDK. Both are legitimate, well-established dependencies for a performance monitoring package. ai
bogus-package bogus-package AI (bogus-package): This is a legitimate Firebase SDK sub-package from Google's monorepo. Short README and missing keywords are typical for internal SDK packages, not spam indicators. ai
dependencies unvetted-dep:@firebase/util AI (dependencies): First-party Firebase SDK dependency from the same Google monorepo; not a third-party risk. ai
dependencies unvetted-dep:@firebase/logger AI (dependencies): First-party Firebase SDK dependency from the same Google monorepo; not a third-party risk. ai
dependencies unvetted-dep:@firebase/installations AI (dependencies): First-party Firebase SDK dependency from the same Google monorepo; not a third-party risk. ai
dependencies unvetted-dep:@firebase/performance-types AI (dependencies): First-party Firebase SDK dependency from the same Google monorepo; not a third-party risk. ai

Versions (showing 100 of 342)

Hide prereleases
Version Deps Published
0.2.12 5 / 19
0.2.11 5 / 19
0.2.10 5 / 19
0.2.9 5 / 19
0.2.8 5 / 19
0.2.7 5 / 17
0.2.6 5 / 13
0.2.5 5 / 13
0.2.4 5 / 13
0.2.3 5 / 13
0.2.2 5 / 13
0.2.1 5 / 13
0.2.0 5 / 13
0.7.11-canary.f4e0086e3 6 / 5
0.7.11-canary.bfb9accdc 6 / 5
0.7.11-canary.ba0bc39bb 6 / 5
0.7.11-canary.742e17a8e 6 / 5
0.7.11-canary.44ad4cc2e 6 / 5
0.7.11-20260317152345 6 / 5
0.7.10-canary.d7b182645 6 / 5
0.7.10-canary.891a0c9d4 6 / 5
0.7.10-canary.843a8d789 6 / 5
0.7.10-canary.792c61671 6 / 5
0.7.10-canary.78384d32c 6 / 5
0.7.10-canary.22476e1bc 6 / 5
0.7.10-20260224183151 6 / 5
0.7.9-firebase-studio-sdk-integration.f7536090e 6 / 5
0.7.9-firebase-studio-sdk-integration.556d1bed2 6 / 5
0.7.9-eap-firestore-pipelines.2.e4cdd2e06 6 / 5
0.7.9-eap-firestore-pipelines.1.f9c4cdec7 6 / 5
0.7.9-canary.f9aaeca46 6 / 5
0.7.9-canary.f9254b6d2 6 / 5
0.7.9-canary.f5fc6bf76 6 / 5
0.7.9-canary.f2ecae7df 6 / 5
0.7.9-canary.f0b0398eb 6 / 5
0.7.9-canary.f06cbf99b 6 / 5
0.7.9-canary.efc0117ae 6 / 5
0.7.9-canary.ea8512812 6 / 5
0.7.9-canary.e6415ddee 6 / 5
0.7.9-canary.e4b2890fd 6 / 5
0.7.9-canary.d818df4e8 6 / 5
0.7.9-canary.d7c311a4b 6 / 5
0.7.9-canary.d5ff5a4b1 6 / 5
0.7.9-canary.d4b22a872 6 / 5
0.7.9-canary.d1d898f55 6 / 5
0.7.9-canary.ccbf7ba36 6 / 5
0.7.9-canary.cc605e728 6 / 5
0.7.9-canary.cbef6c6e5 6 / 5
0.7.9-canary.cb3bdd812 6 / 5
0.7.9-canary.c8263c471 6 / 5
0.7.9-canary.c5f08a9bc 6 / 5
0.7.9-canary.c4a3a5643 6 / 5
0.7.9-canary.c48b47674 6 / 5
0.7.9-canary.c47bd7175 6 / 5
0.7.9-canary.c1237662e 6 / 5
0.7.9-canary.bc5a7c4a7 6 / 5
0.7.9-canary.bc2b2cdea 6 / 5
0.7.9-canary.b7e18d0ff 6 / 5
0.7.9-canary.b2827448b 6 / 5
0.7.9-canary.b228a2ab9 6 / 5
0.7.9-canary.b10a296fa 6 / 5
0.7.9-canary.a4848b401 6 / 5
0.7.9-canary.a09ef786f 6 / 5
0.7.9-canary.9cf4b7e35 6 / 5
0.7.9-canary.9ced4281d 6 / 5
0.7.9-canary.9b8ab02c5 6 / 5
0.7.9-canary.9b63cd60e 6 / 5
0.7.9-canary.984086b0b 6 / 5
0.7.9-canary.93eeffcb3 6 / 5
0.7.9-canary.920624ade 6 / 5
0.7.9-canary.91c218db2 6 / 5
0.7.9-canary.9101b4611 6 / 5
0.7.9-canary.8e26a5590 6 / 5
0.7.9-canary.8bac8f0b2 6 / 5
0.7.9-canary.84b8bed35 6 / 5
0.7.9-canary.8209266c6 6 / 5
0.7.9-canary.817151ee9 6 / 5
0.7.9-canary.8123231a1 6 / 5
0.7.9-canary.7b1e6ec79 6 / 5
0.7.9-canary.7a7634f79 6 / 5
0.7.9-canary.6e0e30317 6 / 5
0.7.9-canary.6abe52967 6 / 5
0.7.9-canary.6ab71fa0b 6 / 5
0.7.9-canary.691a506ec 6 / 5
0.7.9-canary.65a553baf 6 / 5
0.7.9-canary.63167c68a 6 / 5
0.7.9-canary.60d1b18bd 6 / 5
0.7.9-canary.5c7430dea 6 / 5
0.7.9-canary.5c35f514c 6 / 5
0.7.9-canary.59407948d 6 / 5
0.7.9-canary.58ddd6e54 6 / 5
0.7.9-canary.578686b0b 6 / 5
0.7.9-canary.55f3f83a7 6 / 5
0.7.9-canary.5579b387a 6 / 5
0.7.9-canary.5511b4fa7 6 / 5
0.7.9-canary.5501791d0 6 / 5
0.7.9-canary.4d834deb2 6 / 5
0.7.9-canary.4d2ab8507 6 / 5
0.7.9-canary.47f85219d 6 / 5
0.7.9-canary.46fa57f9e 6 / 5
Showing 100 of 342 Next page →

v0.7.11-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.7.11-canary.bfb9accdc

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.7.11-canary.ba0bc39bb

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.7.11-canary.742e17a8e

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.7.11-canary.44ad4cc2e

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

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

v0.7.10-canary.891a0c9d4

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.7.10-canary.843a8d789

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.7.10-canary.792c61671

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.7.10-canary.78384d32c

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.7.10-canary.22476e1bc

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

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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-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.7.9-canary.d5ff5a4b1

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.7.9-canary.d4b22a872

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.7.9-canary.d1d898f55

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.7.9-canary.ccbf7ba36

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.7.9-canary.cc605e728

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.7.9-canary.cbef6c6e5

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.7.9-canary.cb3bdd812

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.7.9-canary.c8263c471

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.7.9-canary.c5f08a9bc

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.7.9-canary.c4a3a5643

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.7.9-canary.c48b47674

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.7.9-canary.c47bd7175

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.7.9-canary.c1237662e

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.7.9-canary.bc5a7c4a7

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.7.9-canary.bc2b2cdea

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.7.9-canary.b7e18d0ff

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.7.9-canary.b2827448b

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.7.9-canary.b228a2ab9

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.7.9-canary.b10a296fa

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.7.9-canary.a4848b401

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.7.9-canary.a09ef786f

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.7.9-canary.9cf4b7e35

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.7.9-canary.9ced4281d

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.7.9-canary.9b8ab02c5

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.7.9-canary.9b63cd60e

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.7.9-canary.984086b0b

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.7.9-canary.93eeffcb3

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.7.9-canary.920624ade

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.7.9-canary.91c218db2

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.7.9-canary.9101b4611

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.7.9-canary.8e26a5590

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.7.9-canary.8bac8f0b2

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.7.9-canary.84b8bed35

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.7.9-canary.8209266c6

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.7.9-canary.817151ee9

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.7.9-canary.8123231a1

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.7.9-canary.7b1e6ec79

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.7.9-canary.7a7634f79

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.7.9-canary.6e0e30317

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.7.9-canary.6abe52967

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.7.9-canary.6ab71fa0b

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.7.9-canary.691a506ec

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.7.9-canary.65a553baf

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.7.9-canary.63167c68a

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.7.9-canary.60d1b18bd

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.7.9-canary.5c7430dea

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.7.9-canary.5c35f514c

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.7.9-canary.59407948d

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.7.9-canary.58ddd6e54

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.7.9-canary.578686b0b

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.7.9-canary.55f3f83a7

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.7.9-canary.5579b387a

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.7.9-canary.5511b4fa7

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.7.9-canary.5501791d0

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.7.9-canary.4d834deb2

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.7.9-canary.4d2ab8507

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.7.9-canary.47f85219d

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.7.9-canary.46fa57f9e

1 finding
INFO No provenance attestation provenance

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