@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 51 of 298)
| Version | Deps | Published |
|---|---|---|
| 1.3.40 | 4 / 1 | |
| 1.3.39 | 4 / 1 | |
| 1.3.38 | 4 / 1 | |
| 1.3.37 | 4 / 1 | |
| 1.3.36 | 4 / 1 | |
| 1.3.35 | 4 / 1 | |
| 1.3.34 | 4 / 1 | |
| 1.3.33 | 4 / 1 | |
| 1.3.32 | 4 / 1 | |
| 1.3.31 | 4 / 1 | |
| 1.3.30 | 4 / 1 | |
| 1.3.29 | 4 / 1 | |
| 1.3.28 | 4 / 1 | |
| 1.3.27 | 4 / 1 | |
| 1.3.26 | 4 / 1 | |
| 1.3.25 | 4 / 1 | |
| 1.3.24 | 4 / 1 | |
| 1.3.23 | 4 / 1 | |
| 1.3.22 | 4 / 1 | |
| 1.3.21 | 4 / 1 | |
| 1.3.20 | 4 / 1 | |
| 1.3.19 | 4 / 1 | |
| 1.3.18 | 4 / 1 | |
| 1.3.17 | 4 / 1 | |
| 1.3.16 | 4 / 1 | |
| 1.3.15 | 4 / 1 | |
| 1.3.14 | 4 / 1 | |
| 1.3.13 | 4 / 1 | |
| 1.3.12 | 4 / 1 | |
| 1.3.11 | 4 / 1 | |
| 1.3.10 | 4 / 1 | |
| 1.3.9 | 4 / 1 | |
| 1.3.8 | 4 / 1 | |
| 1.3.7 | 4 / 1 | |
| 1.3.6 | 4 / 1 | |
| 1.3.5 | 4 / 1 | |
| 1.3.4 | 4 / 1 | |
| 1.3.3 | 4 / 1 | |
| 1.3.2 | 4 / 1 | |
| 1.3.1 | 4 / 1 | |
| 1.3.0 | 4 / 1 | |
| 1.2.30 | 4 / 1 | |
| 1.2.29 | 4 / 1 | |
| 1.2.28 | 4 / 1 | |
| 1.2.27 | 4 / 1 | |
| 1.2.26 | 4 / 1 | |
| 1.2.25 | 4 / 1 | |
| 1.2.24 | 4 / 1 | |
| 1.2.23 | 4 / 1 | |
| 1.2.22 | 4 / 1 | |
| 1.2.21 | 4 / 1 |
v1.3.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.