@record-evolution/widget-table
REWidget widget-table
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
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.1.21 | 2 / 6 | |
| 1.1.20 | 2 / 6 | |
| 1.1.19 | 2 / 6 | |
| 1.1.18 | 2 / 6 | |
| 1.1.17 | 2 / 6 | |
| 1.1.16 | 2 / 6 | |
| 1.1.15 | 2 / 6 | |
| 1.1.14 | 1 / 22 | |
| 1.1.13 | 1 / 22 | |
| 1.1.12 | 1 / 22 | |
| 1.1.11 | 1 / 22 | |
| 1.1.10 | 1 / 22 | |
| 1.1.9 | 1 / 22 | |
| 1.1.8 | 1 / 22 | |
| 1.1.7 | 1 / 22 | |
| 1.1.6 | 1 / 22 | |
| 1.1.5 | 1 / 22 | |
| 1.1.4 | 2 / 22 | |
| 1.1.3 | 2 / 22 | |
| 1.1.2 | 2 / 22 |
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.