@wzyjs/hooks
description
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Absence of provenance is common; no other risk signals present for this package. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.3.41 | 3 / 4 | |
| 0.3.39 | 3 / 4 | |
| 0.3.38 | 3 / 4 | |
| 0.3.37 | 3 / 4 | |
| 0.3.36 | 3 / 4 | |
| 0.3.32 | 3 / 4 | |
| 0.3.31 | 3 / 4 | |
| 0.3.30 | 3 / 4 | |
| 0.3.29 | 5 / 2 | |
| 0.3.27 | 6 / 0 | |
| 0.3.24 | 6 / 0 | |
| 0.3.23 | 6 / 0 | |
| 0.3.22 | 6 / 0 | |
| 0.3.17 | 6 / 0 | |
| 0.3.10 | 6 / 0 | |
| 0.3.9 | 6 / 0 | |
| 0.3.8 | 6 / 0 | |
| 0.3.7 | 6 / 0 | |
| 0.3.6 | 6 / 0 | |
| 0.3.4 | 6 / 0 | |
| 0.3.3 | 4 / 0 | |
| 0.3.2 | 4 / 0 | |
| 0.3.1 | 4 / 0 | |
| 0.3.0 | 4 / 0 | |
| 0.2.83 | 4 / 0 | |
| 0.2.74 | 4 / 0 | |
| 0.2.73 | 4 / 0 | |
| 0.2.72 | 4 / 0 | |
| 0.2.71 | 4 / 0 | |
| 0.2.70 | 4 / 0 | |
| 0.2.69 | 2 / 0 | |
| 0.2.67 | 2 / 0 | |
| 0.2.66 | 2 / 0 | |
| 0.2.65 | 2 / 0 | |
| 0.2.63 | 2 / 0 | |
| 0.2.62 | 2 / 0 | |
| 0.2.61 | 2 / 0 | |
| 0.2.60 | 2 / 0 | |
| 0.2.59 | 2 / 0 | |
| 0.2.58 | 2 / 0 | |
| 0.2.57 | 2 / 0 | |
| 0.2.56 | 2 / 0 | |
| 0.2.55 | 2 / 0 | |
| 0.2.54 | 2 / 0 | |
| 0.2.53 | 2 / 0 | |
| 0.2.52 | 2 / 0 | |
| 0.2.51 | 2 / 0 | |
| 0.2.50 | 2 / 0 | |
| 0.2.49 | 2 / 0 | |
| 0.2.48 | 2 / 0 | |
| 0.2.47 | 3 / 0 | |
| 0.2.44 | 3 / 0 | |
| 0.2.43 | 3 / 0 | |
| 0.2.42 | 3 / 0 | |
| 0.2.41 | 3 / 0 | |
| 0.2.40 | 3 / 0 | |
| 0.2.39 | 3 / 0 | |
| 0.2.38 | 3 / 0 | |
| 0.2.37 | 3 / 0 | |
| 0.2.36 | 3 / 6 | |
| 0.2.27 | 3 / 6 | |
| 0.2.26 | 3 / 6 | |
| 0.2.20 | 3 / 6 | |
| 0.2.14 | 3 / 6 | |
| 0.2.13 | 6 / 3 | |
| 0.2.12 | 6 / 3 | |
| 0.2.9 | 6 / 3 | |
| 0.2.6 | 6 / 3 | |
| 0.2.4 | 6 / 3 | |
| 0.2.2 | 6 / 3 | |
| 0.2.0 | 6 / 3 |
v0.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.