daisyui
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:components/aura/object.js | AI (source-diff): CSS-in-JS style objects serialized as long lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:components/megamenu/object.js | AI (source-diff): CSS-in-JS style objects serialized as long lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:components/otp/object.js | AI (source-diff): CSS-in-JS style objects serialized as long lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:components/fab/object.js | AI (source-diff): CSS style objects with long lines; not obfuscated code. Pattern is stable for daisyUI component files. | ai |
Versions (showing 66 of 166)
| Version | Deps | Published |
|---|---|---|
| 5.1.11 | 0 / 0 | |
| 5.1.10 | 0 / 0 | |
| 5.1.9 | 0 / 0 | |
| 5.1.8 | 0 / 0 | |
| 5.1.7 | 0 / 0 | |
| 5.1.6 | 0 / 0 | |
| 5.1.5 | 0 / 0 | |
| 5.1.4 | 0 / 0 | |
| 5.1.3 | 0 / 0 | |
| 5.1.2 | 0 / 0 | |
| 5.1.1 | 0 / 0 | |
| 5.1.0 | 0 / 0 | |
| 5.0.55 | 0 / 0 | |
| 5.0.54 | 0 / 0 | |
| 5.0.53 | 0 / 0 | |
| 5.0.52 | 0 / 0 | |
| 5.0.51 | 0 / 0 | |
| 5.0.50 | 0 / 0 | |
| 5.0.49 | 0 / 0 | |
| 5.0.48 | 0 / 0 | |
| 5.0.47 | 0 / 0 | |
| 5.0.46 | 0 / 0 | |
| 5.0.43 | 0 / 0 | |
| 5.0.42 | 0 / 0 | |
| 5.0.41 | 0 / 0 | |
| 5.0.40 | 0 / 0 | |
| 5.0.39 | 0 / 0 | |
| 5.0.38 | 0 / 0 | |
| 5.0.37 | 0 / 0 | |
| 5.0.36 | 0 / 0 | |
| 5.0.35 | 0 / 0 | |
| 5.0.34 | 0 / 0 | |
| 5.0.33 | 0 / 0 | |
| 5.0.32 | 0 / 0 | |
| 5.0.31 | 0 / 0 | |
| 5.0.30 | 0 / 0 | |
| 5.0.29 | 0 / 0 | |
| 5.0.28 | 0 / 0 | |
| 5.0.27 | 0 / 0 | |
| 5.0.26 | 0 / 0 | |
| 5.0.25 | 0 / 0 | |
| 5.0.24 | 0 / 0 | |
| 5.0.23 | 0 / 0 | |
| 5.0.22 | 0 / 0 | |
| 5.0.21 | 0 / 0 | |
| 5.0.20 | 0 / 0 | |
| 5.0.19 | 0 / 0 | |
| 5.0.18 | 0 / 0 | |
| 5.0.17 | 0 / 0 | |
| 5.0.16 | 0 / 0 | |
| 5.0.15 | 0 / 0 | |
| 5.0.14 | 0 / 0 | |
| 5.0.13 | 0 / 0 | |
| 5.0.12 | 0 / 0 | |
| 5.0.11 | 0 / 0 | |
| 5.0.10 | 0 / 0 | |
| 5.0.9 | 0 / 0 | |
| 5.0.8 | 0 / 0 | |
| 5.0.7 | 0 / 0 | |
| 5.0.6 | 0 / 0 | |
| 5.0.5 | 0 / 0 | |
| 5.0.4 | 0 / 0 | |
| 5.0.3 | 0 / 0 | |
| 5.0.2 | 0 / 0 | |
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 |
v5.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.