@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 18 of 218)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 1 / 13 | |
| 2.1.2 | 1 / 13 | |
| 2.1.1 | 1 / 13 | |
| 2.1.0 | 1 / 13 | |
| 2.0.13 | 1 / 13 | |
| 2.0.12 | 1 / 13 | |
| 2.0.11 | 1 / 13 | |
| 2.0.10 | 1 / 13 | |
| 2.0.9 | 1 / 13 | |
| 2.0.8 | 1 / 13 | |
| 2.0.7 | 1 / 13 | |
| 2.0.6 | 1 / 13 | |
| 2.0.5 | 1 / 13 | |
| 2.0.4 | 1 / 13 | |
| 2.0.3 | 1 / 13 | |
| 2.0.2 | 1 / 13 | |
| 2.0.1 | 1 / 13 | |
| 2.0.0 | 1 / 13 |
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.