@scaleflex/ui-tw
React UI components library based on Tailwind and ShadCN by Scaleflex Company
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @radix-ui/react-avatar is a well-known Radix UI primitive; consistent with this library's existing Radix dependency set. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): @radix-ui/react-avatar is a well-established Radix UI primitive; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Declared dep for tooltip/popover positioning; used transitively; stable false positive. | ai | |
| phantom-deps | phantom-dep:tw-animate-css | AI (phantom-deps): CSS-only package loaded via Tailwind config, not imported in JS; stable false positive. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Declared runtime dep used by convention in React component libraries; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/lodash.merge | AI (phantom-deps): Type-only package; framework-scoped, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:tailwind-scrollbar | AI (phantom-deps): Tailwind plugin loaded via config, not imported in JS; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Declared dep likely used indirectly via config/build; stable false positive for this package. | ai |
Versions (showing 100 of 103)
| Version | Deps | Published |
|---|---|---|
| 0.0.160 | 32 / 3 | |
| 0.0.159 | 31 / 3 | |
| 0.0.158 | 31 / 3 | |
| 0.0.157 | 31 / 3 | |
| 0.0.156 | 31 / 3 | |
| 0.0.155 | 31 / 3 | |
| 0.0.153 | 31 / 3 | |
| 0.0.152 | 31 / 3 | |
| 0.0.128 | 30 / 3 | |
| 0.0.115 | 28 / 3 | |
| 0.0.114 | 27 / 3 | |
| 0.0.112 | 27 / 3 | |
| 0.0.109 | 27 / 3 | |
| 0.0.108 | 27 / 3 | |
| 0.0.107 | 27 / 3 | |
| 0.0.106 | 27 / 3 | |
| 0.0.105 | 27 / 3 | |
| 0.0.104 | 27 / 3 | |
| 0.0.103 | 27 / 3 | |
| 0.0.102 | 26 / 3 | |
| 0.0.99 | 26 / 3 | |
| 0.0.98 | 25 / 3 | |
| 0.0.96 | 25 / 3 | |
| 0.0.95 | 25 / 3 | |
| 0.0.94 | 25 / 3 | |
| 0.0.93 | 25 / 3 | |
| 0.0.92 | 25 / 3 | |
| 0.0.90 | 25 / 3 | |
| 0.0.89 | 25 / 3 | |
| 0.0.86 | 25 / 3 | |
| 0.0.85 | 25 / 3 | |
| 0.0.83 | 25 / 3 | |
| 0.0.82 | 25 / 3 | |
| 0.0.80 | 25 / 3 | |
| 0.0.79 | 25 / 3 | |
| 0.0.78 | 25 / 3 | |
| 0.0.77 | 25 / 3 | |
| 0.0.76 | 25 / 3 | |
| 0.0.75 | 25 / 3 | |
| 0.0.74 | 25 / 3 | |
| 0.0.72 | 25 / 3 | |
| 0.0.71 | 25 / 3 | |
| 0.0.69 | 25 / 3 | |
| 0.0.68 | 25 / 3 | |
| 0.0.66 | 25 / 3 | |
| 0.0.64 | 24 / 3 | |
| 0.0.63 | 24 / 3 | |
| 0.0.62 | 24 / 3 | |
| 0.0.61 | 24 / 3 | |
| 0.0.60 | 24 / 3 | |
| 0.0.59 | 24 / 3 | |
| 0.0.58 | 24 / 3 | |
| 0.0.57 | 24 / 3 | |
| 0.0.55 | 24 / 3 | |
| 0.0.54 | 24 / 3 | |
| 0.0.53 | 24 / 3 | |
| 0.0.52 | 24 / 3 | |
| 0.0.50 | 24 / 3 | |
| 0.0.49 | 24 / 3 | |
| 0.0.48 | 24 / 3 | |
| 0.0.47 | 24 / 3 | |
| 0.0.46 | 24 / 3 | |
| 0.0.45 | 24 / 3 | |
| 0.0.44 | 24 / 3 | |
| 0.0.42 | 24 / 3 | |
| 0.0.41 | 22 / 3 | |
| 0.0.40 | 22 / 3 | |
| 0.0.39 | 22 / 3 | |
| 0.0.38 | 22 / 3 | |
| 0.0.37 | 22 / 3 | |
| 0.0.36 | 22 / 3 | |
| 0.0.35 | 19 / 3 | |
| 0.0.34 | 18 / 3 | |
| 0.0.33 | 18 / 3 | |
| 0.0.32 | 18 / 3 | |
| 0.0.31 | 18 / 3 | |
| 0.0.30 | 18 / 3 | |
| 0.0.29 | 16 / 3 | |
| 0.0.28 | 16 / 3 | |
| 0.0.27 | 16 / 3 | |
| 0.0.26 | 15 / 3 | |
| 0.0.25 | 15 / 3 | |
| 0.0.24 | 14 / 4 | |
| 0.0.22 | 14 / 3 | |
| 0.0.21 | 14 / 3 | |
| 0.0.20 | 14 / 3 | |
| 0.0.19 | 14 / 3 | |
| 0.0.18 | 14 / 3 | |
| 0.0.17 | 13 / 3 | |
| 0.0.16 | 13 / 3 | |
| 0.0.15 | 13 / 3 | |
| 0.0.14 | 13 / 3 | |
| 0.0.13 | 13 / 3 | |
| 0.0.11 | 12 / 3 | |
| 0.0.10 | 12 / 3 | |
| 0.0.9 | 12 / 3 | |
| 0.0.8 | 12 / 3 | |
| 0.0.7 | 12 / 3 | |
| 0.0.6 | 11 / 3 | |
| 0.0.5 | 11 / 3 |
v0.0.160
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vitaly.shaposhnik) than the most recent previously approved version (dmitry.stremous) on 2026-06-04, but vitaly.shaposhnik is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.159
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dmitry.stremous) than the most recent previously approved version (vitaly.shaposhnik) on 2026-06-03, but dmitry.stremous is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.158
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vitaly.shaposhnik) than the most recent previously approved version (philipka) on 2026-05-28, but vitaly.shaposhnik is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.