@synerise/ds-items-roll
ItemsRoll 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@synerise/ds-popconfirm | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-button | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-search | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-divider | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tooltip | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-menu | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-dropdown | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-list-item | AI (dependencies): Internal Synerise DS sibling package; consistent monorepo pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Synerise DS monorepo package; no provenance is consistent across all their releases. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 1.5.30 | 13 / 2 | |
| 1.5.29 | 13 / 2 | |
| 1.5.28 | 13 / 2 | |
| 1.5.27 | 13 / 2 | |
| 1.5.26 | 13 / 2 | |
| 1.5.25 | 13 / 2 | |
| 1.5.24 | 13 / 2 | |
| 1.5.23 | 13 / 2 | |
| 1.5.22 | 13 / 2 | |
| 1.5.21 | 13 / 2 | |
| 1.5.20 | 13 / 2 | |
| 1.5.19 | 13 / 2 | |
| 1.5.18 | 13 / 2 | |
| 1.5.17 | 13 / 2 | |
| 1.5.16 | 13 / 2 | |
| 1.5.15 | 12 / 1 | |
| 1.5.14 | 12 / 1 | |
| 1.5.13 | 12 / 1 | |
| 1.5.12 | 12 / 1 | |
| 1.5.11 | 11 / 1 | |
| 1.5.10 | 11 / 1 | |
| 1.5.9 | 11 / 1 | |
| 1.5.8 | 11 / 1 | |
| 1.5.7 | 11 / 1 | |
| 1.5.6 | 11 / 1 | |
| 1.5.5 | 11 / 1 | |
| 1.5.4 | 11 / 1 | |
| 1.5.3 | 11 / 1 | |
| 1.5.2 | 11 / 1 | |
| 1.5.1 | 11 / 1 | |
| 1.5.0 | 11 / 1 | |
| 1.4.3 | 10 / 1 | |
| 1.4.2 | 10 / 1 | |
| 1.4.1 | 10 / 1 | |
| 1.4.0 | 10 / 1 | |
| 1.3.3 | 10 / 1 | |
| 1.3.2 | 10 / 1 | |
| 1.3.1 | 10 / 1 | |
| 1.3.0 | 10 / 1 | |
| 1.2.4 | 10 / 0 | |
| 1.2.3 | 10 / 0 | |
| 1.2.2 | 10 / 0 | |
| 1.2.1 | 10 / 0 | |
| 1.2.0 | 10 / 0 | |
| 1.1.9 | 10 / 0 | |
| 1.1.8 | 10 / 0 | |
| 1.1.7 | 10 / 0 | |
| 1.1.6 | 10 / 0 | |
| 1.1.5 | 10 / 0 | |
| 1.1.4 | 10 / 0 | |
| 1.1.3 | 10 / 0 |
v1.5.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.