@gentleduck/registry-ui
Styled Tailwind components for Duck 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React UI library; react-dom is a core peer dependency correctly declared and used. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Tailwind-based UI package; tailwindcss is a build-time dependency correctly declared. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 20 / 4 | |
| 0.4.4 | 20 / 4 | |
| 0.4.3 | 20 / 4 | |
| 0.4.2 | 20 / 4 | |
| 0.4.1 | 20 / 4 | |
| 0.4.0 | 20 / 4 | |
| 0.3.3 | 20 / 4 | |
| 0.3.2 | 20 / 4 | |
| 0.3.1 | 20 / 4 | |
| 0.3.0 | 20 / 4 | |
| 0.2.12 | 20 / 4 | |
| 0.2.11 | 20 / 4 | |
| 0.2.10 | 20 / 4 | |
| 0.2.9 | 20 / 4 | |
| 0.2.8 | 20 / 4 | |
| 0.2.6 | 20 / 4 | |
| 0.2.5 | 20 / 4 | |
| 0.2.4 | 20 / 4 | |
| 0.2.3 | 20 / 4 | |
| 0.2.1 | 20 / 4 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.