@revealui/presentation
Native React UI components built on Tailwind v4 — zero external UI dependencies (only clsx + CVA). Buttons, forms, dialogs, navigation, and more.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 0 / 15 | |
| 0.4.1 | 0 / 15 | |
| 0.4.0 | 0 / 15 | |
| 0.3.6 | 0 / 15 | |
| 0.3.5 | 0 / 15 | |
| 0.3.4 | 0 / 15 | |
| 0.3.3 | 0 / 15 | |
| 0.3.2 | 2 / 15 | |
| 0.3.0 | 2 / 15 | |
| 0.2.0 | 2 / 14 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.