@platforma-open/milaboratories.miltenyi-tcr-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@platforma-open/milaboratories.miltenyi-tcr-clonotyping.ui | AI (phantom-deps): Same-org sub-package referenced via block config, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.miltenyi-tcr-clonotyping.model | AI (phantom-deps): Same-org sub-package referenced via block config, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.miltenyi-tcr-clonotyping.workflow | AI (phantom-deps): Same-org sub-package referenced via block config, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/model | AI (phantom-deps): Referenced in block config metadata, not direct import; stable false positive for this aggregator pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentionally tiny aggregator/manifest package; metadata signals are expected for this block-registry pattern. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 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.4 | 4 / 1 | |
| 1.2.3 | 4 / 1 | |
| 1.2.2 | 4 / 1 | |
| 1.2.1 | 4 / 1 | |
| 1.2.0 | 4 / 1 | |
| 1.1.3 | 4 / 1 |
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.