@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 — the axios compromise (March 2026) relied on exactly this gap.
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 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 2.15.0 | 18 / 8 | |
| 2.14.25 | 18 / 8 | |
| 2.14.24 | 18 / 8 | |
| 2.14.23 | 18 / 8 | |
| 2.14.22 | 18 / 8 | |
| 2.14.21 | 18 / 8 | |
| 2.14.20 | 18 / 8 | |
| 2.14.19 | 18 / 8 | |
| 2.14.18 | 18 / 8 | |
| 2.14.17 | 18 / 8 | |
| 2.14.16 | 18 / 8 | |
| 2.14.14 | 18 / 8 | |
| 2.14.13 | 18 / 8 | |
| 2.14.12 | 18 / 8 | |
| 2.14.11 | 18 / 8 | |
| 2.14.10 | 18 / 8 | |
| 2.14.9 | 18 / 8 | |
| 2.14.8 | 18 / 8 | |
| 2.14.7 | 18 / 8 | |
| 2.14.6 | 18 / 8 | |
| 2.14.5 | 18 / 8 | |
| 2.14.4 | 18 / 8 | |
| 2.14.3 | 18 / 8 | |
| 2.14.2 | 18 / 8 | |
| 2.14.1 | 18 / 8 | |
| 2.14.0 | 18 / 8 | |
| 2.13.5 | 18 / 8 | |
| 2.13.4 | 18 / 8 | |
| 2.13.3 | 18 / 8 | |
| 2.13.2 | 18 / 8 | |
| 2.13.1 | 18 / 8 | |
| 2.13.0 | 18 / 8 | |
| 2.12.15 | 18 / 8 | |
| 2.12.14 | 18 / 8 | |
| 2.12.13 | 18 / 8 | |
| 2.12.12 | 18 / 8 | |
| 2.12.11 | 18 / 8 | |
| 2.12.10 | 18 / 8 | |
| 2.12.9 | 18 / 8 | |
| 2.12.8 | 18 / 8 | |
| 2.12.7 | 18 / 8 | |
| 2.12.6 | 18 / 8 | |
| 2.12.5 | 18 / 8 | |
| 2.12.4 | 18 / 8 | |
| 2.12.3 | 18 / 8 | |
| 2.12.2 | 18 / 8 | |
| 2.12.1 | 18 / 8 | |
| 2.12.0 | 18 / 8 | |
| 2.11.9 | 18 / 8 | |
| 2.11.8 | 18 / 8 | |
| 2.11.7 | 18 / 8 | |
| 2.11.6 | 18 / 8 | |
| 2.11.5 | 18 / 8 | |
| 2.11.4 | 18 / 8 |
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.