@platforma-open/milaboratories.clonotype-clustering.workflow
Tengo-based template
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): mike-ainsel is an established publisher (512 approved) in the same org ecosystem; transition appears legitimate. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/workflow-tengo | AI (phantom-deps): Tengo workflow packages reference deps via build config, not direct imports; stable FP for this package family. | ai | |
| phantom-deps | phantom-dep:@platforma-open/soedinglab.software-mmseqs2 | AI (phantom-deps): Same-org software dep referenced via Tengo build config, not direct import; stable FP. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.clonotype-clustering.software | AI (phantom-deps): Same-org software dep referenced via Tengo build config, not direct import; stable FP. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 3 / 1 | |
| 4.0.1 | 3 / 1 | |
| 4.0.0 | 3 / 1 | |
| 3.28.0 | 3 / 1 | |
| 3.27.1 | 3 / 1 | |
| 3.27.0 | 3 / 1 | |
| 3.26.0 | 3 / 1 | |
| 3.25.4 | 3 / 1 | |
| 3.25.3 | 3 / 1 | |
| 3.25.2 | 3 / 1 | |
| 3.25.1 | 3 / 1 | |
| 3.25.0 | 3 / 1 | |
| 3.24.0 | 3 / 1 | |
| 3.23.0 | 3 / 5 | |
| 3.22.5 | 3 / 5 | |
| 3.22.4 | 3 / 5 | |
| 3.22.3 | 3 / 5 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.