@platforma-open/milaboratories.demultiplex-fastq
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@platforma-open/milaboratories.demultiplex-fastq.ui | AI (dependencies): Same-org sub-package in a known monorepo; consistent pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Org-scoped block package; no provenance is consistent across all versions in this registry. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/model | AI (phantom-deps): Used in block config/metadata resolution, not direct JS imports; stable false positive for this package type. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.demultiplex-fastq.ui | AI (phantom-deps): Sibling sub-package referenced via block.components config path, not JS import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated block-tools manifest package; tiny payload and missing metadata are structural, not spam indicators. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.demultiplex-fastq.workflow | AI (phantom-deps): Sibling sub-package referenced via block.components config path, not JS import. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.demultiplex-fastq.model | AI (phantom-deps): Sibling sub-package referenced via block.components config path, not JS import. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Description lives in block.meta.description; top-level field intentionally omitted by block-tools toolchain. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 4 / 1 | |
| 1.2.4 | 4 / 1 | |
| 1.2.3 | 4 / 1 | |
| 1.2.2 | 4 / 1 | |
| 1.2.1 | 4 / 1 | |
| 1.1.0 | 4 / 1 |
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.