@sqlrooms/ui
A comprehensive UI component library for SQLRooms applications, built on top of React and Tailwind CSS. This package provides a collection of reusable, accessible, and customizable components designed to create consistent and beautiful user interfaces.
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:zod | AI (phantom-deps): zod is a peer/config dependency for form validation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): hookform resolver used in config/examples; stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @sqlrooms/ui; Levenshtein match to 'qs' is noise from short suffix. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @sqlrooms/ui; Levenshtein match to 'joi' is noise from short suffix. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @sqlrooms/ui; Levenshtein match to 'yup' is noise from short suffix. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @sqlrooms/ui; Levenshtein match to 'uuid' is noise from short suffix. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): Tailwind plugin declared as dep and referenced in config; not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/typography | AI (phantom-deps): Tailwind plugin declared as dep and referenced in config; not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Declared runtime dep used by react-day-picker integration; config-file reference is expected. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @sqlrooms/ui; Levenshtein match to 'pg' is noise from short suffix. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 39 / 0 | |
| 0.27.0 | 39 / 0 | |
| 0.26.0 | 38 / 0 | |
| 0.24.27 | 38 / 0 | |
| 0.24.26 | 38 / 0 | |
| 0.24.25 | 38 / 0 | |
| 0.24.24 | 38 / 0 | |
| 0.24.23 | 38 / 0 | |
| 0.24.22 | 38 / 0 | |
| 0.24.21 | 38 / 0 | |
| 0.24.20 | 38 / 0 | |
| 0.24.19 | 38 / 0 | |
| 0.24.18 | 38 / 0 | |
| 0.24.17 | 38 / 0 | |
| 0.24.16 | 37 / 0 | |
| 0.24.15 | 37 / 0 | |
| 0.24.14 | 37 / 0 | |
| 0.24.13 | 37 / 0 | |
| 0.24.12 | 37 / 0 | |
| 0.24.11 | 37 / 0 | |
| 0.24.10 | 37 / 0 | |
| 0.24.9 | 37 / 0 | |
| 0.24.8 | 37 / 0 | |
| 0.24.7 | 37 / 0 | |
| 0.24.6 | 37 / 0 | |
| 0.24.5 | 37 / 0 | |
| 0.24.4 | 37 / 0 | |
| 0.24.3 | 37 / 0 | |
| 0.24.2 | 37 / 0 | |
| 0.24.1 | 37 / 0 | |
| 0.24.0 | 37 / 0 | |
| 0.23.0 | 37 / 0 | |
| 0.22.0 | 37 / 0 | |
| 0.21.0 | 37 / 0 | |
| 0.20.0 | 37 / 0 | |
| 0.19.2 | 37 / 0 | |
| 0.19.1 | 37 / 0 | |
| 0.19.0 | 37 / 0 | |
| 0.18.1 | 37 / 0 | |
| 0.18.0 | 37 / 0 | |
| 0.17.0 | 37 / 0 | |
| 0.16.4 | 37 / 0 | |
| 0.16.3 | 37 / 0 | |
| 0.16.2 | 37 / 0 | |
| 0.16.1 | 37 / 0 | |
| 0.16.0 | 37 / 0 | |
| 0.15.0 | 37 / 0 | |
| 0.14.0 | 32 / 0 | |
| 0.13.2 | 32 / 0 | |
| 0.13.1 | 32 / 0 | |
| 0.13.0 | 32 / 0 |
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.