@synerise/ds-card-tabs
CardTabs 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-inline-edit | AI (dependencies): Same-org monorepo sibling; Synerise publisher has 103 approved packages. | ai | |
| dependencies | unvetted-dep:@synerise/ds-menu | AI (dependencies): Same-org monorepo sibling; Synerise publisher has 103 approved packages. | ai | |
| dependencies | unvetted-dep:@synerise/ds-cruds | AI (dependencies): Same-org monorepo sibling; Synerise publisher has 103 approved packages. | ai | |
| dependencies | unvetted-dep:@synerise/ds-button | AI (dependencies): Same-org monorepo sibling; Synerise publisher has 103 approved packages. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tooltip | AI (dependencies): Same-org monorepo sibling; Synerise publisher has 103 approved packages. | ai | |
| dependencies | unvetted-dep:@synerise/ds-dropdown | AI (dependencies): Same-org monorepo sibling; Synerise publisher has 103 approved packages. | ai | |
| dependencies | unvetted-dep:@synerise/ds-typography | AI (dependencies): Same-org monorepo sibling; Synerise publisher has 103 approved packages. | ai | |
| provenance | no-provenance | AI (provenance): Established Synerise DS publisher; no provenance is consistent across all 475 versions. | ai | |
| phantom-deps | phantom-dep:@synerise/ds-menu | AI (phantom-deps): Same-org sibling dep in a monorepo; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 1.5.41 | 10 / 0 | |
| 1.5.40 | 10 / 0 | |
| 1.5.39 | 10 / 0 | |
| 1.5.38 | 10 / 0 | |
| 1.5.37 | 10 / 0 | |
| 1.5.36 | 10 / 0 | |
| 1.5.35 | 10 / 0 | |
| 1.5.34 | 10 / 0 | |
| 1.5.33 | 10 / 0 | |
| 1.5.32 | 10 / 0 | |
| 1.5.31 | 10 / 0 | |
| 1.5.30 | 10 / 0 | |
| 1.5.29 | 10 / 0 | |
| 1.5.28 | 10 / 0 | |
| 1.5.27 | 10 / 0 | |
| 1.5.26 | 10 / 0 | |
| 1.5.25 | 10 / 0 | |
| 1.5.24 | 10 / 0 | |
| 1.5.23 | 10 / 0 | |
| 1.5.22 | 10 / 0 | |
| 1.5.21 | 10 / 0 | |
| 1.5.20 | 10 / 0 | |
| 1.5.19 | 10 / 0 | |
| 1.5.18 | 10 / 0 | |
| 1.5.17 | 10 / 0 | |
| 1.5.16 | 10 / 0 | |
| 1.5.15 | 10 / 0 | |
| 1.5.14 | 10 / 0 | |
| 1.5.13 | 10 / 0 | |
| 1.5.12 | 10 / 0 | |
| 1.5.11 | 10 / 0 | |
| 1.5.10 | 10 / 0 | |
| 1.5.9 | 10 / 0 | |
| 1.5.8 | 10 / 0 | |
| 1.5.7 | 10 / 0 | |
| 1.5.6 | 10 / 0 | |
| 1.5.5 | 10 / 0 | |
| 1.5.4 | 10 / 0 | |
| 1.5.3 | 10 / 0 | |
| 1.5.2 | 10 / 0 | |
| 1.5.1 | 10 / 0 | |
| 1.5.0 | 10 / 0 | |
| 1.4.27 | 10 / 0 | |
| 1.4.26 | 10 / 0 | |
| 1.4.25 | 10 / 0 | |
| 1.4.24 | 10 / 0 | |
| 1.4.23 | 10 / 0 | |
| 1.4.22 | 10 / 0 | |
| 1.4.21 | 10 / 0 | |
| 1.4.19 | 10 / 0 | |
| 1.4.18 | 10 / 0 | |
| 1.4.17 | 10 / 0 | |
| 1.4.16 | 10 / 0 | |
| 1.4.15 | 10 / 0 | |
| 1.4.14 | 10 / 0 | |
| 1.4.13 | 10 / 0 | |
| 1.4.12 | 10 / 0 | |
| 1.4.11 | 10 / 0 | |
| 1.4.10 | 10 / 0 | |
| 1.4.9 | 10 / 0 | |
| 1.4.8 | 10 / 0 | |
| 1.4.7 | 10 / 0 | |
| 1.4.6 | 10 / 0 | |
| 1.4.5 | 10 / 0 | |
| 1.4.4 | 10 / 0 | |
| 1.4.3 | 10 / 0 | |
| 1.4.2 | 10 / 0 | |
| 1.4.1 | 10 / 0 | |
| 1.4.0 | 10 / 0 | |
| 1.3.3 | 10 / 0 | |
| 1.3.2 | 10 / 0 | |
| 1.3.1 | 10 / 0 | |
| 1.3.0 | 10 / 0 |
v1.5.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.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.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.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.