@synerise/ds-completed-within
CompletedWithin 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-select | AI (dependencies): First-party sibling package from same Synerise design system org. | ai | |
| dependencies | unvetted-dep:@synerise/ds-button | AI (dependencies): First-party sibling package from same Synerise design system org. | ai | |
| dependencies | unvetted-dep:@synerise/ds-input | AI (dependencies): First-party sibling package from same Synerise design system org. | ai | |
| dependencies | unvetted-dep:@synerise/ds-input-number | AI (dependencies): First-party sibling package from same Synerise design system org. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tooltip | AI (dependencies): First-party sibling package from same Synerise design system org. | ai | |
| dependencies | unvetted-dep:@synerise/ds-dropdown | AI (dependencies): First-party sibling package from same Synerise design system org. | ai | |
| provenance | no-provenance | AI (provenance): Established design system package; lack of Sigstore provenance is consistent across all 303 versions and poses no elevated risk here. | ai |
Versions (showing 51 of 72)
| Version | Deps | Published |
|---|---|---|
| 1.2.25 | 8 / 1 | |
| 1.2.24 | 8 / 1 | |
| 1.2.23 | 8 / 1 | |
| 1.2.22 | 8 / 1 | |
| 1.2.21 | 8 / 1 | |
| 1.2.20 | 8 / 1 | |
| 1.2.19 | 8 / 1 | |
| 1.2.18 | 8 / 1 | |
| 1.2.17 | 8 / 1 | |
| 1.2.16 | 8 / 1 | |
| 1.2.15 | 8 / 1 | |
| 1.2.14 | 8 / 1 | |
| 1.2.13 | 8 / 1 | |
| 1.2.12 | 8 / 1 | |
| 1.2.11 | 8 / 1 | |
| 1.2.10 | 8 / 1 | |
| 1.2.9 | 8 / 1 | |
| 1.2.8 | 8 / 1 | |
| 1.2.7 | 8 / 0 | |
| 1.2.6 | 8 / 0 | |
| 1.2.5 | 8 / 0 | |
| 1.2.4 | 8 / 0 | |
| 1.2.3 | 8 / 0 | |
| 1.2.2 | 8 / 0 | |
| 1.2.1 | 8 / 0 | |
| 1.2.0 | 8 / 0 | |
| 1.1.13 | 8 / 0 | |
| 1.1.12 | 8 / 0 | |
| 1.1.11 | 8 / 0 | |
| 1.1.10 | 8 / 0 | |
| 1.1.9 | 8 / 0 | |
| 1.1.8 | 8 / 0 | |
| 1.1.7 | 8 / 0 | |
| 1.1.6 | 8 / 0 | |
| 1.1.5 | 8 / 0 | |
| 1.1.4 | 8 / 0 | |
| 1.1.3 | 8 / 0 | |
| 1.1.2 | 8 / 0 | |
| 1.1.1 | 8 / 0 | |
| 1.1.0 | 8 / 0 | |
| 1.0.39 | 8 / 0 | |
| 1.0.38 | 8 / 0 | |
| 1.0.37 | 8 / 0 | |
| 1.0.36 | 8 / 0 | |
| 1.0.35 | 8 / 0 | |
| 1.0.34 | 8 / 0 | |
| 1.0.33 | 8 / 0 | |
| 1.0.31 | 8 / 0 | |
| 1.0.30 | 8 / 0 | |
| 1.0.29 | 8 / 0 | |
| 1.0.28 | 8 / 0 |
v1.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
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.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
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.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.