@ws-ui/ui-components
Qodly Design System - UI component library
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tailwind-scrollbar | AI (phantom-deps): Declared runtime dep; used in Tailwind config, not directly imported in JS source. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Bundled library; same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:simplebar-react | AI (phantom-deps): Bundled library; same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/sortable | AI (phantom-deps): Bundled library; same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/modifiers | AI (phantom-deps): Bundled library; same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/utilities | AI (phantom-deps): Bundled library; same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): Bundled library; same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:simplebar | AI (phantom-deps): Bundled library; deps used via build pipeline, not direct imports detectable by static analysis. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Bundled library; same false-positive pattern as other phantom-dep findings. | ai | |
| phantom-deps | phantom-dep:@ws-ui/icons | AI (phantom-deps): Same-org dep; bundled library pattern. | ai | |
| phantom-deps | phantom-dep:re-resizable | AI (phantom-deps): Bundled library; same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-virtual | AI (phantom-deps): Bundled library; same false-positive pattern. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.0.33 | 12 / 46 | |
| 1.0.32 | 12 / 46 | |
| 1.0.31 | 12 / 46 | |
| 1.0.30 | 12 / 46 | |
| 1.0.29 | 12 / 46 | |
| 1.0.28 | 12 / 46 | |
| 1.0.27 | 12 / 46 | |
| 1.0.26 | 12 / 46 | |
| 1.0.25 | 12 / 46 | |
| 1.0.24 | 12 / 46 | |
| 1.0.23 | 12 / 46 | |
| 1.0.22 | 12 / 46 | |
| 1.0.21 | 12 / 46 | |
| 1.0.20 | 12 / 46 | |
| 1.0.19 | 11 / 46 | |
| 1.0.17 | 11 / 46 | |
| 1.0.16 | 11 / 46 | |
| 1.0.15 | 11 / 46 | |
| 1.0.14 | 11 / 46 | |
| 1.0.13 | 11 / 46 | |
| 1.0.12 | 11 / 46 | |
| 1.0.11 | 11 / 46 | |
| 1.0.9 | 11 / 46 | |
| 1.0.8 | 11 / 46 | |
| 1.0.7 | 11 / 46 | |
| 1.0.6 | 9 / 43 | |
| 1.0.5 | 9 / 43 | |
| 1.0.4 | 9 / 43 | |
| 1.0.3 | 9 / 43 | |
| 1.0.2 | 9 / 45 | |
| 1.0.1 | 9 / 45 | |
| 1.0.0 | 9 / 45 |
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.