@synerise/ds-table
Table 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:unit-to-px | AI (dependencies): Legitimate utility package; stable dependency for this design system component. | ai | |
| dependencies | unvetted-dep:@synerise/ds-scrollbar | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-checkbox | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-dropdown | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-skeleton | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-copy-icon | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-list-item | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tag | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-flag | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-icon | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-menu | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tags | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-alert | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-badge | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-input | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-modal | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-button | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-result | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-search | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-status | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tooltip | AI (dependencies): Same-org sibling component; stable pattern across all ds-table versions. | ai | |
| phantom-deps | phantom-dep:@synerise/ds-list-item | AI (phantom-deps): Same-org sibling dep; phantom detection is unreliable for monorepo component packages. | ai | |
| phantom-deps | phantom-dep:@synerise/ds-pagination | AI (phantom-deps): Same-org sibling dep; phantom detection is unreliable for monorepo component packages. | ai | |
| phantom-deps | phantom-dep:@types/react-window | AI (phantom-deps): Type-only package; may be used implicitly by framework tooling. | ai | |
| phantom-deps | phantom-dep:@synerise/ds-select | AI (phantom-deps): Same-org sibling dep; phantom detection is unreliable for monorepo component packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Component library README linking to design system docs is expected; not a spam/phishing indicator. | ai |
Versions (showing 88 of 88)
| Version | Deps | Published |
|---|---|---|
| 1.11.3 | 41 / 7 | |
| 1.11.2 | 41 / 7 | |
| 1.11.1 | 41 / 7 | |
| 1.11.0 | 41 / 7 | |
| 1.10.12 | 41 / 7 | |
| 1.10.11 | 41 / 7 | |
| 1.10.10 | 41 / 7 | |
| 1.10.9 | 41 / 7 | |
| 1.10.8 | 41 / 7 | |
| 1.10.7 | 41 / 7 | |
| 1.10.6 | 41 / 7 | |
| 1.10.5 | 41 / 7 | |
| 1.10.4 | 41 / 7 | |
| 1.10.3 | 41 / 7 | |
| 1.10.2 | 41 / 7 | |
| 1.10.1 | 41 / 7 | |
| 1.10.0 | 41 / 7 | |
| 1.9.14 | 41 / 7 | |
| 1.9.13 | 41 / 7 | |
| 1.9.12 | 41 / 7 | |
| 1.9.11 | 41 / 7 | |
| 1.9.10 | 41 / 7 | |
| 1.9.9 | 41 / 7 | |
| 1.9.8 | 41 / 7 | |
| 1.9.7 | 41 / 7 | |
| 1.9.6 | 41 / 7 | |
| 1.9.5 | 41 / 7 | |
| 1.9.4 | 41 / 7 | |
| 1.9.3 | 41 / 7 | |
| 1.9.2 | 41 / 7 | |
| 1.9.1 | 41 / 7 | |
| 1.9.0 | 36 / 2 | |
| 1.8.5 | 36 / 2 | |
| 1.8.4 | 36 / 2 | |
| 1.8.3 | 36 / 2 | |
| 1.8.2 | 36 / 2 | |
| 1.8.1 | 34 / 2 | |
| 1.8.0 | 34 / 2 | |
| 1.7.8 | 34 / 2 | |
| 1.7.7 | 34 / 2 | |
| 1.7.6 | 34 / 2 | |
| 1.7.5 | 34 / 2 | |
| 1.7.4 | 34 / 2 | |
| 1.7.3 | 34 / 2 | |
| 1.7.2 | 34 / 0 | |
| 1.7.1 | 33 / 0 | |
| 1.7.0 | 33 / 0 | |
| 1.6.11 | 33 / 0 | |
| 1.6.10 | 33 / 0 | |
| 1.6.9 | 33 / 0 | |
| 1.6.8 | 33 / 0 | |
| 1.6.7 | 33 / 0 | |
| 1.6.6 | 33 / 0 | |
| 1.6.5 | 33 / 0 | |
| 1.6.4 | 32 / 0 | |
| 1.6.3 | 32 / 0 | |
| 1.6.1 | 32 / 0 | |
| 1.6.0 | 32 / 0 | |
| 1.5.13 | 34 / 0 | |
| 1.5.12 | 34 / 0 | |
| 1.5.11 | 34 / 0 | |
| 1.5.10 | 34 / 0 | |
| 1.5.9 | 35 / 0 | |
| 1.5.8 | 35 / 0 | |
| 1.5.7 | 35 / 0 | |
| 1.5.6 | 35 / 0 | |
| 1.5.5 | 35 / 0 | |
| 1.5.4 | 35 / 0 | |
| 1.5.3 | 35 / 0 | |
| 1.5.2 | 35 / 0 | |
| 1.5.1 | 35 / 0 | |
| 1.5.0 | 35 / 0 | |
| 1.4.3 | 35 / 0 | |
| 1.4.2 | 35 / 0 | |
| 1.4.1 | 35 / 0 | |
| 1.4.0 | 35 / 0 | |
| 1.3.2 | 35 / 0 | |
| 1.3.1 | 35 / 0 | |
| 1.3.0 | 35 / 0 | |
| 1.2.2 | 35 / 0 | |
| 1.2.1 | 35 / 0 | |
| 1.2.0 | 35 / 0 | |
| 1.1.14 | 35 / 0 | |
| 1.1.13 | 35 / 0 | |
| 1.1.12 | 35 / 0 | |
| 1.1.11 | 35 / 0 | |
| 1.1.10 | 35 / 0 | |
| 1.1.9 | 35 / 0 |
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.