@synerise/ds-cruds
Cruds UI Component for the Synerise Design System
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): Established Synerise DS package; no provenance is consistent across all their releases. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 1.1.16 | 3 / 1 | |
| 1.1.15 | 3 / 1 | |
| 1.1.14 | 3 / 1 | |
| 1.1.13 | 3 / 1 | |
| 1.1.12 | 3 / 1 | |
| 1.1.11 | 3 / 1 | |
| 1.1.10 | 3 / 1 | |
| 1.1.9 | 3 / 1 | |
| 1.1.8 | 3 / 1 | |
| 1.1.7 | 3 / 1 | |
| 1.1.6 | 3 / 1 | |
| 1.1.5 | 3 / 1 | |
| 1.1.4 | 3 / 1 | |
| 1.1.3 | 3 / 1 | |
| 1.1.2 | 3 / 1 | |
| 1.1.1 | 3 / 1 | |
| 1.1.0 | 3 / 1 | |
| 1.0.37 | 3 / 0 | |
| 1.0.36 | 3 / 0 | |
| 1.0.35 | 3 / 0 | |
| 1.0.34 | 3 / 0 | |
| 1.0.33 | 3 / 0 | |
| 1.0.32 | 3 / 0 | |
| 1.0.31 | 3 / 0 | |
| 1.0.30 | 3 / 0 | |
| 1.0.29 | 3 / 0 | |
| 1.0.28 | 3 / 0 | |
| 1.0.27 | 3 / 0 | |
| 1.0.26 | 3 / 0 | |
| 1.0.25 | 3 / 0 | |
| 1.0.24 | 3 / 0 | |
| 1.0.23 | 3 / 0 | |
| 1.0.22 | 3 / 0 | |
| 1.0.21 | 3 / 0 | |
| 1.0.20 | 3 / 0 | |
| 1.0.19 | 3 / 0 | |
| 1.0.18 | 3 / 0 | |
| 1.0.17 | 3 / 0 | |
| 1.0.16 | 3 / 0 | |
| 1.0.15 | 3 / 0 | |
| 1.0.14 | 3 / 0 | |
| 1.0.13 | 3 / 0 | |
| 1.0.12 | 3 / 0 | |
| 1.0.11 | 3 / 0 | |
| 1.0.10 | 3 / 0 | |
| 1.0.9 | 3 / 0 | |
| 1.0.8 | 3 / 0 | |
| 1.0.7 | 3 / 0 | |
| 1.0.6 | 3 / 0 | |
| 1.0.5 | 3 / 0 | |
| 1.0.4 | 3 / 0 |
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.