@funkit/wagmi-tools
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package published via GitHub Actions; missing provenance is common and not a risk signal here. | ai |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 3.0.91 | 3 / 4 | |
| 3.0.90 | 3 / 4 | |
| 3.0.89 | 3 / 4 | |
| 3.0.88 | 3 / 4 | |
| 3.0.87 | 3 / 4 | |
| 3.0.86 | 3 / 4 | |
| 3.0.85 | 3 / 4 | |
| 3.0.84 | 3 / 4 | |
| 3.0.83 | 3 / 4 | |
| 3.0.81 | 3 / 4 | |
| 3.0.80 | 3 / 4 | |
| 3.0.79 | 3 / 4 | |
| 3.0.78 | 3 / 4 | |
| 3.0.77 | 3 / 4 | |
| 3.0.76 | 3 / 4 | |
| 3.0.75 | 3 / 4 | |
| 3.0.74 | 3 / 4 | |
| 3.0.73 | 3 / 4 | |
| 3.0.72 | 3 / 4 | |
| 3.0.71 | 3 / 4 | |
| 3.0.70 | 3 / 4 | |
| 3.0.69 | 3 / 4 | |
| 3.0.68 | 3 / 4 | |
| 3.0.67 | 3 / 4 | |
| 3.0.66 | 3 / 4 | |
| 3.0.65 | 3 / 4 | |
| 3.0.64 | 3 / 4 | |
| 3.0.63 | 3 / 4 | |
| 3.0.62 | 3 / 4 | |
| 3.0.61 | 3 / 4 | |
| 3.0.60 | 3 / 4 | |
| 3.0.59 | 3 / 4 | |
| 3.0.58 | 3 / 4 | |
| 3.0.57 | 3 / 4 | |
| 3.0.56 | 3 / 4 | |
| 3.0.55 | 3 / 4 | |
| 3.0.54 | 3 / 4 | |
| 3.0.53 | 3 / 4 | |
| 3.0.52 | 3 / 4 | |
| 3.0.51 | 3 / 4 | |
| 3.0.50 | 3 / 4 | |
| 3.0.49 | 3 / 4 | |
| 3.0.48 | 3 / 4 | |
| 3.0.47 | 3 / 4 | |
| 3.0.46 | 3 / 4 | |
| 3.0.45 | 3 / 4 | |
| 3.0.44 | 3 / 4 | |
| 3.0.43 | 3 / 4 | |
| 3.0.42 | 3 / 4 | |
| 3.0.41 | 3 / 4 | |
| 3.0.40 | 3 / 4 | |
| 3.0.39 | 3 / 4 | |
| 3.0.38 | 3 / 4 | |
| 3.0.37 | 3 / 4 | |
| 3.0.36 | 3 / 4 | |
| 3.0.35 | 3 / 4 | |
| 3.0.34 | 3 / 4 | |
| 3.0.33 | 3 / 4 | |
| 3.0.32 | 3 / 4 | |
| 3.0.31 | 3 / 4 | |
| 3.0.30 | 3 / 4 | |
| 3.0.29 | 3 / 4 | |
| 3.0.28 | 3 / 4 | |
| 3.0.27 | 3 / 4 | |
| 3.0.26 | 3 / 4 | |
| 3.0.25 | 4 / 4 | |
| 3.0.24 | 4 / 4 | |
| 3.0.23 | 4 / 4 | |
| 3.0.22 | 3 / 4 | |
| 3.0.21 | 3 / 4 | |
| 3.0.20 | 3 / 6 | |
| 3.0.19 | 3 / 7 | |
| 3.0.18 | 3 / 7 | |
| 3.0.17 | 3 / 7 | |
| 3.0.16 | 3 / 8 | |
| 3.0.15 | 3 / 8 | |
| 3.0.14 | 3 / 8 | |
| 3.0.13 | 3 / 8 | |
| 3.0.12 | 3 / 8 | |
| 3.0.11 | 3 / 8 | |
| 3.0.10 | 3 / 8 | |
| 3.0.9 | 3 / 8 | |
| 3.0.8 | 3 / 8 | |
| 3.0.7 | 3 / 8 | |
| 3.0.6 | 3 / 8 | |
| 3.0.5 | 3 / 8 | |
| 3.0.4 | 3 / 8 | |
| 3.0.3 | 3 / 8 | |
| 3.0.2 | 3 / 8 | |
| 3.0.1 | 3 / 8 | |
| 3.0.0 | 3 / 8 |
v3.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.