@platforma-open/milaboratories.mixcr-scfv-clonotyping
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.mixcr-scfv-clonotyping.workflow | AI (dependencies): Same-org sub-component dependency; consistent with the block-component architecture used across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentional tiny manifest/aggregator package; pattern is consistent across all versions of this org's block packages. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/block-tools | AI (phantom-deps): Used in build scripts/config, not imported directly; stable false positive for this package type. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.mixcr-scfv-clonotyping.ui | AI (phantom-deps): Referenced via block.components config path, not direct import; expected pattern for this org's block manifests. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.mixcr-scfv-clonotyping.model | AI (phantom-deps): Referenced via block.components config path, not direct import; expected pattern for this org's block manifests. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.mixcr-scfv-clonotyping.workflow | AI (phantom-deps): Referenced via block.components config path, not direct import; expected pattern for this org's block manifests. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.4.10 | 4 / 1 | |
| 3.4.9 | 4 / 1 | |
| 3.4.8 | 4 / 1 | |
| 3.4.7 | 4 / 1 | |
| 3.4.6 | 4 / 1 | |
| 3.4.5 | 4 / 1 | |
| 3.4.4 | 4 / 1 | |
| 3.4.3 | 4 / 1 | |
| 3.4.2 | 4 / 1 | |
| 3.4.1 | 4 / 1 | |
| 3.4.0 | 4 / 1 | |
| 3.3.0 | 4 / 1 | |
| 3.2.2 | 4 / 1 | |
| 3.2.1 | 4 / 1 | |
| 3.2.0 | 4 / 1 | |
| 3.1.0 | 4 / 1 | |
| 3.0.13 | 4 / 1 | |
| 3.0.12 | 4 / 1 | |
| 3.0.11 | 4 / 1 | |
| 3.0.10 | 4 / 1 | |
| 3.0.9 | 4 / 1 | |
| 3.0.8 | 4 / 1 | |
| 3.0.7 | 4 / 1 | |
| 3.0.6 | 4 / 1 | |
| 3.0.5 | 4 / 1 | |
| 3.0.4 | 4 / 1 | |
| 3.0.3 | 4 / 1 | |
| 3.0.2 | 4 / 1 | |
| 3.0.1 | 4 / 1 | |
| 3.0.0 | 4 / 1 |
v3.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-06, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-05, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.