@milaboratories/uikit
```bash npm i @milaboratories/uikit --save ```
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/d3-axis | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/d3-array | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/d3-scale | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/d3-selection | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/sortablejs | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:@vue/test-utils | AI (phantom-deps): Test utility; used in test config, not directly imported in source, stable false positive. | ai | |
| phantom-deps | phantom-dep:sortablejs | AI (phantom-deps): Referenced in config files; indirect usage pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:resize-observer-polyfill | AI (phantom-deps): Polyfill referenced in config; indirect usage pattern is stable for this package. | ai |
Versions (showing 100 of 218)
| Version | Deps | Published |
|---|---|---|
| 2.10.23 | 18 / 8 | |
| 2.10.22 | 18 / 8 | |
| 2.10.21 | 18 / 8 | |
| 2.10.20 | 18 / 8 | |
| 2.10.19 | 18 / 8 | |
| 2.10.18 | 18 / 8 | |
| 2.10.17 | 18 / 8 | |
| 2.10.16 | 18 / 8 | |
| 2.10.15 | 18 / 11 | |
| 2.10.14 | 18 / 11 | |
| 2.10.13 | 18 / 11 | |
| 2.10.12 | 18 / 11 | |
| 2.10.11 | 18 / 11 | |
| 2.10.10 | 18 / 11 | |
| 2.10.9 | 18 / 11 | |
| 2.10.8 | 18 / 11 | |
| 2.10.7 | 18 / 11 | |
| 2.10.6 | 18 / 11 | |
| 2.10.5 | 18 / 11 | |
| 2.10.4 | 18 / 11 | |
| 2.10.3 | 18 / 11 | |
| 2.10.2 | 18 / 11 | |
| 2.10.1 | 18 / 11 | |
| 2.10.0 | 18 / 11 | |
| 2.9.1 | 18 / 11 | |
| 2.9.0 | 18 / 11 | |
| 2.8.9 | 18 / 11 | |
| 2.8.8 | 18 / 11 | |
| 2.8.7 | 18 / 11 | |
| 2.8.6 | 18 / 11 | |
| 2.8.5 | 18 / 11 | |
| 2.8.4 | 18 / 9 | |
| 2.8.3 | 18 / 9 | |
| 2.8.2 | 18 / 9 | |
| 2.8.1 | 18 / 9 | |
| 2.8.0 | 18 / 9 | |
| 2.7.3 | 18 / 9 | |
| 2.7.2 | 18 / 9 | |
| 2.7.1 | 18 / 9 | |
| 2.7.0 | 18 / 9 | |
| 2.6.5 | 18 / 9 | |
| 2.6.4 | 18 / 9 | |
| 2.6.3 | 18 / 9 | |
| 2.6.2 | 18 / 9 | |
| 2.6.1 | 18 / 9 | |
| 2.6.0 | 18 / 9 | |
| 2.5.7 | 18 / 9 | |
| 2.5.6 | 18 / 9 | |
| 2.5.4 | 18 / 9 | |
| 2.5.3 | 18 / 9 | |
| 2.5.2 | 18 / 9 | |
| 2.5.1 | 18 / 9 | |
| 2.2.47 | 2 / 15 | |
| 2.2.46 | 2 / 15 | |
| 2.2.45 | 1 / 14 | |
| 2.2.44 | 1 / 14 | |
| 2.2.43 | 1 / 14 | |
| 2.2.42 | 1 / 14 | |
| 2.2.41 | 1 / 14 | |
| 2.2.40 | 1 / 14 | |
| 2.2.39 | 1 / 14 | |
| 2.2.38 | 1 / 14 | |
| 2.2.37 | 1 / 14 | |
| 2.2.36 | 1 / 14 | |
| 2.2.35 | 1 / 14 | |
| 2.2.34 | 1 / 14 | |
| 2.2.33 | 1 / 14 | |
| 2.2.32 | 1 / 14 | |
| 2.2.31 | 1 / 14 | |
| 2.2.30 | 1 / 14 | |
| 2.2.29 | 1 / 14 | |
| 2.2.28 | 1 / 14 | |
| 2.2.27 | 1 / 14 | |
| 2.2.26 | 1 / 13 | |
| 2.2.25 | 1 / 13 | |
| 2.2.24 | 1 / 13 | |
| 2.2.23 | 1 / 13 | |
| 2.2.22 | 1 / 13 | |
| 2.2.21 | 1 / 13 | |
| 2.2.20 | 1 / 13 | |
| 2.2.19 | 1 / 13 | |
| 2.2.18 | 1 / 13 | |
| 2.2.17 | 1 / 13 | |
| 2.2.16 | 1 / 13 | |
| 2.2.15 | 1 / 13 | |
| 2.2.14 | 1 / 13 | |
| 2.2.13 | 1 / 13 | |
| 2.2.12 | 1 / 13 | |
| 2.2.11 | 1 / 13 | |
| 2.2.10 | 1 / 13 | |
| 2.2.9 | 1 / 13 | |
| 2.2.8 | 1 / 13 | |
| 2.2.7 | 1 / 13 | |
| 2.2.6 | 1 / 13 | |
| 2.2.5 | 1 / 13 | |
| 2.2.4 | 1 / 13 | |
| 2.2.3 | 1 / 13 | |
| 2.2.2 | 1 / 13 | |
| 2.2.1 | 1 / 13 | |
| 2.2.0 | 1 / 13 |
v2.10.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.