@darajs/ui-utils
General utilities for the Dara UI framework
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI/CD is confirmed by SLSA provenance attestation; expected for this package going forward. | ai | |
| dependencies | unvetted-dep:tinykeys | AI (dependencies): tinykeys is a legitimate, widely-used keyboard shortcut library; stable false positive for this package. | ai |
Versions (showing 56 of 156)
| Version | Deps | Published |
|---|---|---|
| 1.16.15 | 6 / 20 | |
| 1.16.14 | 6 / 20 | |
| 1.16.13 | 6 / 20 | |
| 1.16.12 | 6 / 20 | |
| 1.16.11 | 6 / 20 | |
| 1.16.10 | 6 / 20 | |
| 1.16.9 | 6 / 20 | |
| 1.16.8 | 6 / 20 | |
| 1.16.7 | 6 / 20 | |
| 1.16.6 | 6 / 20 | |
| 1.16.5 | 5 / 20 | |
| 1.16.4 | 5 / 20 | |
| 1.16.3 | 5 / 20 | |
| 1.16.2 | 5 / 20 | |
| 1.16.1 | 5 / 20 | |
| 1.16.0 | 5 / 20 | |
| 1.15.7 | 5 / 20 | |
| 1.15.6 | 5 / 20 | |
| 1.15.5 | 5 / 20 | |
| 1.15.4 | 5 / 20 | |
| 1.15.3 | 5 / 20 | |
| 1.15.2 | 5 / 20 | |
| 1.15.1 | 5 / 20 | |
| 1.15.0 | 5 / 20 | |
| 1.14.9 | 5 / 20 | |
| 1.14.8 | 5 / 20 | |
| 1.14.7 | 5 / 20 | |
| 1.14.6 | 5 / 20 | |
| 1.14.5 | 5 / 20 | |
| 1.14.4 | 5 / 20 | |
| 1.14.3 | 5 / 20 | |
| 1.14.2 | 5 / 20 | |
| 1.14.1 | 5 / 20 | |
| 1.14.0 | 5 / 20 | |
| 1.13.1 | 5 / 20 | |
| 1.13.0 | 5 / 20 | |
| 1.12.7 | 5 / 20 | |
| 1.12.6 | 5 / 20 | |
| 1.12.5 | 5 / 20 | |
| 1.12.4 | 5 / 20 | |
| 1.12.3 | 5 / 20 | |
| 1.12.2 | 5 / 20 | |
| 1.12.1 | 5 / 20 | |
| 1.11.5 | 5 / 20 | |
| 1.11.4 | 5 / 20 | |
| 1.11.3 | 5 / 20 | |
| 1.11.2 | 5 / 20 | |
| 1.10.3 | 5 / 20 | |
| 1.10.2 | 5 / 20 | |
| 1.10.1 | 5 / 20 | |
| 1.10.0 | 5 / 20 | |
| 1.9.6 | 5 / 20 | |
| 1.9.5 | 5 / 20 | |
| 1.9.4 | 5 / 20 | |
| 1.9.3 | 5 / 20 | |
| 1.9.2 | 5 / 20 |
v1.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.