@synerise/ds-manageable-list
ManageableList 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-tag | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-icon | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-list | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-menu | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-input | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-modal | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-utils | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-avatar | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-button | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-result | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-divider | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tooltip | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-dropdown | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-sortable | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-popconfirm | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-typography | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-inline-edit | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| phantom-deps | phantom-dep:@synerise/ds-menu | AI (phantom-deps): Same-org sibling; phantom-dep heuristic false positive for monorepo packages. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with 1871 approved packages; lack of provenance is common and not a risk here. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 1.8.3 | 19 / 0 | |
| 1.8.2 | 19 / 0 | |
| 1.8.1 | 19 / 0 | |
| 1.8.0 | 19 / 0 | |
| 1.7.26 | 19 / 0 | |
| 1.7.25 | 19 / 0 | |
| 1.7.24 | 19 / 0 | |
| 1.7.23 | 19 / 0 | |
| 1.7.22 | 19 / 0 | |
| 1.7.21 | 19 / 0 | |
| 1.7.20 | 19 / 0 | |
| 1.7.19 | 19 / 0 | |
| 1.7.18 | 19 / 0 | |
| 1.7.17 | 19 / 0 | |
| 1.7.16 | 19 / 0 | |
| 1.7.15 | 19 / 0 | |
| 1.7.14 | 19 / 0 | |
| 1.7.13 | 19 / 0 | |
| 1.7.12 | 19 / 0 | |
| 1.7.11 | 19 / 0 | |
| 1.7.10 | 19 / 0 | |
| 1.7.9 | 19 / 0 | |
| 1.7.8 | 19 / 0 | |
| 1.7.7 | 19 / 0 | |
| 1.7.6 | 19 / 0 | |
| 1.7.5 | 19 / 0 | |
| 1.7.4 | 19 / 0 | |
| 1.7.3 | 19 / 0 | |
| 1.7.2 | 19 / 0 | |
| 1.7.1 | 19 / 0 | |
| 1.7.0 | 19 / 0 | |
| 1.6.13 | 19 / 0 | |
| 1.6.12 | 19 / 0 | |
| 1.6.11 | 19 / 0 | |
| 1.6.10 | 19 / 0 | |
| 1.6.9 | 19 / 0 | |
| 1.6.8 | 19 / 0 | |
| 1.6.7 | 19 / 0 | |
| 1.6.6 | 19 / 0 | |
| 1.6.5 | 19 / 0 | |
| 1.6.4 | 19 / 0 | |
| 1.6.3 | 19 / 0 | |
| 1.6.2 | 19 / 0 | |
| 1.6.1 | 19 / 0 | |
| 1.6.0 | 19 / 0 | |
| 1.5.3 | 19 / 0 | |
| 1.5.2 | 19 / 0 | |
| 1.5.1 | 19 / 0 | |
| 1.5.0 | 19 / 0 | |
| 1.4.5 | 19 / 0 | |
| 1.4.4 | 19 / 0 |
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
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.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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.