@themeshift/ui
ThemeShift UI makes creating your own theme-aware components easy as pie 🥧
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@themeshift/vite-plugin | AI (phantom-deps): Same-org build plugin; used at build time, not imported in library source. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@themeshift/vite-plugin-themeshift | AI (phantom-deps): Same-org build plugin; phantom-dep heuristic fires because it's a build-time dep used in config, not runtime import. | ai | |
| phantom-deps | phantom-dep:@fontsource-variable/noto-sans | AI (phantom-deps): Font package referenced in CSS/config rather than JS imports; phantom-dep is a stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; name similarity to joi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; name similarity to yup is coincidental. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; name similarity to uuid is coincidental, not a squatting attempt. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Referenced in build config; normal for bundled component libraries. | ai | |
| phantom-deps | phantom-dep:react-textarea-autosize | AI (phantom-deps): Referenced in build config; normal for bundled component libraries. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Referenced in build config; normal for bundled component libraries. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; name similarity to pg is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; name similarity to qs is coincidental. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 4 / 36 | |
| 0.4.0 | 4 / 36 | |
| 0.3.0 | 4 / 35 | |
| 0.2.0 | 4 / 35 | |
| 0.1.14 | 3 / 35 | |
| 0.1.13 | 2 / 36 | |
| 0.1.12 | 2 / 36 | |
| 0.1.11 | 2 / 36 | |
| 0.1.10 | 2 / 36 | |
| 0.1.9 | 2 / 36 | |
| 0.1.8 | 2 / 36 | |
| 0.1.7 | 2 / 36 | |
| 0.1.5 | 2 / 36 | |
| 0.1.4 | 3 / 26 | |
| 0.1.3 | 3 / 26 | |
| 0.1.2 | 3 / 26 | |
| 0.1.1 | 3 / 26 |
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.