@uxf/ui
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:@floating-ui/react | AI (phantom-deps): UI library re-exports dependencies; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:jump.js | AI (phantom-deps): UI library re-exports dependencies; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@uxf/core | AI (phantom-deps): Same-org scoped dependency; re-exported by UI library. | ai | |
| phantom-deps | phantom-dep:react-dropzone | AI (phantom-deps): UI library re-exports dependencies; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@uxf/core-react | AI (phantom-deps): Same-org scoped dependency; re-exported by UI library. | ai | |
| phantom-deps | phantom-dep:@uxf/datepicker | AI (phantom-deps): Same-org scoped dependency; re-exported by UI library. | ai | |
| phantom-deps | phantom-dep:@headlessui/react | AI (phantom-deps): UI library re-exports dependencies; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): UI library re-exports dependencies; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:color2k | AI (phantom-deps): UI library re-exports dependencies; stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @uxf/ui from established org; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @uxf/ui from established org; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @uxf/ui from established org; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @uxf/ui from established org; not a typosquat of yup. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-supplied Tailwind config path in a build-time token generator script; expected pattern. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @uxf/ui from established org; not a typosquat of uuid. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 11.118.2 | 0 / 12 | |
| 11.118.0 | 0 / 12 | |
| 11.117.2 | 0 / 12 | |
| 11.115.0 | 0 / 12 | |
| 11.114.0 | 0 / 12 | |
| 11.113.0 | 0 / 12 | |
| 11.112.1 | 0 / 12 | |
| 11.112.0 | 0 / 12 | |
| 11.111.2 | 0 / 12 | |
| 11.111.0 | 0 / 12 | |
| 11.110.1 | 0 / 12 | |
| 11.110.0 | 0 / 12 | |
| 11.108.0 | 0 / 12 | |
| 11.107.0 | 5 / 8 | |
| 11.106.0 | 10 / 3 | |
| 11.105.0 | 10 / 3 | |
| 11.104.0 | 10 / 3 | |
| 11.102.0 | 10 / 3 | |
| 11.101.0 | 10 / 3 | |
| 11.100.1 | 10 / 3 | |
| 11.100.0 | 10 / 3 | |
| 11.99.1 | 10 / 3 | |
| 11.99.0 | 10 / 3 | |
| 11.97.0 | 10 / 3 | |
| 11.96.1 | 10 / 3 | |
| 11.95.1 | 10 / 3 | |
| 11.95.0 | 10 / 3 | |
| 11.94.0 | 10 / 3 | |
| 11.93.3 | 10 / 3 | |
| 11.93.2 | 10 / 3 | |
| 11.93.1 | 10 / 3 | |
| 11.93.0 | 10 / 3 | |
| 11.92.3 | 10 / 3 | |
| 11.92.2 | 10 / 3 | |
| 11.92.1 | 10 / 3 | |
| 11.92.0 | 10 / 3 | |
| 11.91.0 | 9 / 3 | |
| 11.90.1 | 9 / 3 | |
| 11.90.0 | 9 / 3 | |
| 11.89.0 | 9 / 3 | |
| 11.88.2 | 9 / 3 | |
| 11.88.1 | 9 / 3 | |
| 11.88.0 | 9 / 3 | |
| 11.87.0 | 9 / 3 | |
| 11.86.0 | 9 / 3 | |
| 11.85.0 | 10 / 4 | |
| 11.80.6 | 10 / 3 | |
| 11.80.4 | 10 / 3 | |
| 11.80.2 | 10 / 3 | |
| 11.80.1 | 10 / 3 | |
| 11.80.0 | 10 / 3 |
v11.118.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.117.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.114.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.99.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.96.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.95.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.90.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.88.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.88.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.80.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.80.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.80.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.