@milaboratories/milaboratories.ui-examples
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is consistent across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with 479 versions; no provenance is consistent pattern. | ai | |
| phantom-deps | phantom-dep:@milaboratories/milaboratories.ui-examples.model | AI (phantom-deps): Same-org sub-package referenced in block config, not imported directly. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/model | AI (phantom-deps): Block manifest package; deps referenced in config/block metadata, not directly imported in JS. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Block manifest packages are intentionally tiny with minimal metadata; pattern is consistent across 479 versions. | ai | |
| phantom-deps | phantom-dep:@milaboratories/milaboratories.ui-examples.workflow | AI (phantom-deps): Same-org sub-package referenced in block config, not imported directly. | ai | |
| phantom-deps | phantom-dep:@milaboratories/milaboratories.ui-examples.ui | AI (phantom-deps): Same-org sub-package referenced in block config, not imported directly. | ai |
Versions (showing 9 of 311)
| Version | Deps | Published |
|---|---|---|
| 1.0.248 | 4 / 1 | |
| 1.0.247 | 4 / 1 | |
| 1.0.246 | 4 / 1 | |
| 1.0.244 | 4 / 1 | |
| 1.0.243 | 4 / 1 | |
| 1.0.242 | 4 / 1 | |
| 1.0.241 | 4 / 1 | |
| 1.0.240 | 4 / 1 | |
| 1.0.239 | 4 / 1 |
v1.0.248
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.247
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.246
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.244
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.242
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.241
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.240
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.