← Home

@firebase/component

npm Repository Homepage

Firebase Component Platform

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 account; publisher transitions from human maintainers to this bot are standard practice for the Firebase JS SDK. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of individual maintainers in favor of google-wombot automation is consistent with Google's Firebase SDK release process. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a TypeScript compiler helper injected at build time; not directly imported in source but legitimately required as a runtime dependency. Standard false positive for TypeScript packages. ai
provenance no-provenance AI (provenance): Official Firebase SDK package from Google; provenance attestation was not standard practice at time of publication. Stable false positive for this package. ai

Versions (showing 100 of 301)

Hide prereleases
Version Deps Published
0.7.0-canary.e25317f9f 2 / 3
0.7.0-canary.d818df4e8 2 / 3
0.7.0-canary.d7c311a4b 2 / 3
0.7.0-canary.d5ff5a4b1 2 / 3
0.7.0-canary.d4b22a872 2 / 3
0.7.0-canary.d1d898f55 2 / 3
0.7.0-canary.ccbf7ba36 2 / 3
0.7.0-canary.cc605e728 2 / 3
0.7.0-canary.cbef6c6e5 2 / 3
0.7.0-canary.cb3bdd812 2 / 3
0.7.0-canary.c8263c471 2 / 3
0.7.0-canary.c5f08a9bc 2 / 3
0.7.0-canary.c4a3a5643 2 / 3
0.7.0-canary.c48b47674 2 / 3
0.7.0-canary.c47bd7175 2 / 3
0.7.0-canary.c1237662e 2 / 3
0.7.0-canary.bc5a7c4a7 2 / 3
0.7.0-canary.bc2b2cdea 2 / 3
0.7.0-canary.b9209dc91 2 / 3
0.7.0-canary.b7e18d0ff 2 / 3
0.7.0-canary.b2827448b 2 / 3
0.7.0-canary.b228a2ab9 2 / 3
0.7.0-canary.b10a296fa 2 / 3
0.7.0-canary.a4897a621 2 / 3
0.7.0-canary.a4848b401 2 / 3
0.7.0-canary.a09ef786f 2 / 3
0.7.0-canary.9cf4b7e35 2 / 3
0.7.0-canary.9ced4281d 2 / 3
0.7.0-canary.9b8ab02c5 2 / 3
0.7.0-canary.9b63cd60e 2 / 3
0.7.0-canary.984086b0b 2 / 3
0.7.0-canary.93eeffcb3 2 / 3
0.7.0-canary.920624ade 2 / 3
0.7.0-canary.91c218db2 2 / 3
0.7.0-canary.9101b4611 2 / 3
0.7.0-canary.8e26a5590 2 / 3
0.7.0-canary.8bac8f0b2 2 / 3
0.7.0-canary.84b8bed35 2 / 3
0.7.0-canary.8209266c6 2 / 3
0.7.0-canary.817151ee9 2 / 3
0.7.0-canary.8123231a1 2 / 3
0.7.0-canary.7b1e6ec79 2 / 3
0.7.0-canary.7a7634f79 2 / 3
0.7.0-canary.6e0e30317 2 / 3
0.7.0-canary.6abe52967 2 / 3
0.7.0-canary.6ab71fa0b 2 / 3
0.7.0-canary.691a506ec 2 / 3
0.7.0-canary.65a553baf 2 / 3
0.7.0-canary.63167c68a 2 / 3
0.7.0-canary.60d1b18bd 2 / 3
0.7.0-canary.5c7430dea 2 / 3
0.7.0-canary.5c35f514c 2 / 3
0.7.0-canary.58ddd6e54 2 / 3
0.7.0-canary.578686b0b 2 / 3
0.7.0-canary.56fbe5207 2 / 3
0.7.0-canary.55f3f83a7 2 / 3
0.7.0-canary.5579b387a 2 / 3
0.7.0-canary.5511b4fa7 2 / 3
0.7.0-canary.5501791d0 2 / 3
0.7.0-canary.4d834deb2 2 / 3
0.7.0-canary.4d2ab8507 2 / 3
0.7.0-canary.492353771 2 / 3
0.7.0-canary.47f85219d 2 / 3
0.7.0-canary.46fa57f9e 2 / 3
0.7.0-canary.44d9891f9 2 / 3
0.7.0-canary.44d8d742f 2 / 3
0.7.0-canary.43276b041 2 / 3
0.7.0-canary.35b284af4 2 / 3
0.7.0-canary.2e7432986 2 / 3
0.7.0-canary.2bd48a604 2 / 3
0.7.0-canary.261508183 2 / 3
0.7.0-canary.2596dd1b5 2 / 3
0.7.0-canary.22e0a1adb 2 / 3
0.7.0-canary.2058432e6 2 / 3
0.7.0-canary.1e406a2b7 2 / 3
0.7.0-canary.1bcf83d7f 2 / 3
0.7.0-canary.180b1ad9b 2 / 3
0.7.0-canary.120a30838 2 / 3
0.7.0-canary.0ffcb26af 2 / 3
0.7.0-canary.0bb2fe636 2 / 3
0.7.0-canary.095c098de 2 / 3
0.7.0-canary.08e3acdf0 2 / 3
0.7.0-canary.0800a8bed 2 / 3
0.7.0-canary.06ab5c4f9 2 / 3
0.7.0-canary.02280d747 2 / 3
0.7.0-caching-fdc.9f17eac6e 2 / 3
0.7.0-20250716201504 2 / 3
0.7.0-20250716004940 2 / 3
0.7.0-20250715195345 2 / 3
0.6.18-canary.f18b25f73 2 / 3
0.6.18-canary.f11b55294 2 / 3
0.6.18-canary.d91169f06 2 / 3
0.6.18-canary.cb19688bf 2 / 3
0.6.18-canary.a9be6757f 2 / 3
0.6.18-canary.9771bffad 2 / 3
0.6.18-canary.574800585 2 / 3
0.6.18-canary.5200f7bb7 2 / 3
0.6.18-canary.2d720995d 2 / 3
0.6.18-canary.2b5731292 2 / 3
0.6.18-canary.25b60fdaa 2 / 3
Showing 100 of 301 Next page →

v0.7.0-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.7.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-canary.b9209dc91

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.0-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.0-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.0-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.0-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.0-canary.a4897a621

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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-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.0-canary.56fbe5207

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.0-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.0-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.0-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.0-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.0-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.0-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.0-canary.492353771

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

v0.7.0-canary.44d9891f9

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.0-canary.44d8d742f

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.0-canary.43276b041

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.0-canary.35b284af4

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.0-canary.2e7432986

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.0-canary.2bd48a604

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.0-canary.261508183

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.0-canary.2596dd1b5

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.0-canary.22e0a1adb

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.0-canary.2058432e6

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.0-canary.1e406a2b7

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.0-canary.1bcf83d7f

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.0-canary.180b1ad9b

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.0-canary.120a30838

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.0-canary.0ffcb26af

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.0-canary.0bb2fe636

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.0-canary.095c098de

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.0-canary.08e3acdf0

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.0-canary.0800a8bed

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.0-canary.06ab5c4f9

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.0-canary.02280d747

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.0-caching-fdc.9f17eac6e

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

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

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

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.6.18-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.6.18-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.6.18-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.6.18-canary.cb19688bf

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.6.18-canary.a9be6757f

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.6.18-canary.9771bffad

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.6.18-canary.574800585

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.6.18-canary.5200f7bb7

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.6.18-canary.2d720995d

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.6.18-canary.2b5731292

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.6.18-canary.25b60fdaa

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.