@platforma-open/milaboratories.samples-and-data
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Wrapper/manifest package pattern; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 74 versions; org-wide pattern, not a new signal. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.samples-and-data.model | AI (phantom-deps): Sub-component referenced in block config, not imported directly; expected pattern. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/model | AI (phantom-deps): Deps referenced in block config paths, not JS imports; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Aggregator/manifest package by design; tiny payload and no keywords are expected for this package type. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.samples-and-data.workflow | AI (phantom-deps): Sub-component referenced in block config, not imported directly; expected pattern. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.samples-and-data.ui | AI (phantom-deps): Sub-component referenced in block config, not imported directly; expected pattern. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 1.18.1 | 0 / 9 | |
| 1.18.0 | 0 / 9 | |
| 1.17.5 | 4 / 2 | |
| 1.17.4 | 4 / 2 | |
| 1.17.3 | 4 / 1 | |
| 1.17.2 | 4 / 1 | |
| 1.17.1 | 4 / 1 | |
| 1.17.0 | 4 / 1 | |
| 1.16.0 | 4 / 1 | |
| 1.15.0 | 4 / 1 | |
| 1.14.0 | 4 / 1 | |
| 1.13.3 | 4 / 1 | |
| 1.13.2 | 4 / 1 | |
| 1.13.1 | 4 / 1 | |
| 1.13.0 | 4 / 1 | |
| 1.12.4 | 4 / 1 | |
| 1.12.3 | 4 / 1 | |
| 1.12.2 | 4 / 1 | |
| 1.12.1 | 4 / 1 | |
| 1.12.0 | 4 / 1 | |
| 1.11.1 | 4 / 1 | |
| 1.11.0 | 4 / 1 | |
| 1.10.19 | 4 / 1 | |
| 1.10.18 | 4 / 1 | |
| 1.10.17 | 4 / 1 | |
| 1.10.16 | 4 / 1 | |
| 1.10.15 | 4 / 1 | |
| 1.10.14 | 4 / 1 | |
| 1.10.13 | 4 / 1 | |
| 1.10.12 | 4 / 1 | |
| 1.10.11 | 4 / 1 | |
| 1.10.10 | 4 / 1 | |
| 1.10.9 | 4 / 1 | |
| 1.10.8 | 4 / 1 | |
| 1.10.7 | 4 / 1 | |
| 1.10.6 | 4 / 1 | |
| 1.10.5 | 4 / 1 | |
| 1.10.4 | 4 / 1 | |
| 1.10.3 | 4 / 1 | |
| 1.10.2 | 4 / 1 | |
| 1.10.1 | 4 / 1 | |
| 1.10.0 | 4 / 1 | |
| 1.9.11 | 4 / 1 | |
| 1.9.10 | 4 / 1 | |
| 1.9.9 | 4 / 1 | |
| 1.9.8 | 4 / 1 | |
| 1.9.7 | 4 / 1 | |
| 1.9.6 | 4 / 1 | |
| 1.9.5 | 4 / 1 | |
| 1.9.4 | 4 / 1 | |
| 1.9.3 | 4 / 1 | |
| 1.9.2 | 4 / 1 | |
| 1.9.1 | 4 / 1 | |
| 1.9.0 | 4 / 1 | |
| 1.8.8 | 4 / 1 | |
| 1.8.7 | 4 / 1 | |
| 1.8.6 | 4 / 1 | |
| 1.8.5 | 4 / 1 | |
| 1.8.3 | 4 / 1 | |
| 1.8.2 | 4 / 1 | |
| 1.8.1 | 4 / 1 | |
| 1.8.0 | 4 / 1 | |
| 1.7.1 | 4 / 1 | |
| 1.7.0 | 4 / 3 | |
| 1.6.7 | 4 / 3 | |
| 1.6.6 | 4 / 3 | |
| 1.6.5 | 4 / 3 | |
| 1.6.4 | 4 / 3 | |
| 1.6.3 | 4 / 3 | |
| 1.6.2 | 4 / 3 | |
| 1.6.1 | 4 / 3 | |
| 1.6.0 | 4 / 3 | |
| 1.5.3 | 4 / 3 | |
| 1.5.2 | 4 / 3 | |
| 1.5.1 | 4 / 3 | |
| 1.5.0 | 4 / 3 | |
| 1.4.1 | 4 / 3 | |
| 1.4.0 | 4 / 3 |
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
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.6.6
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.6.5
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.6.4
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.6.3
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.6.2
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.6.1
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.6.0
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.5.3
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.5.2
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.5.1
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.5.0
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.4.1
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.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.