@platforma-open/milaboratories.clonotype-enrichment.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 in the same org with 915 approved packages; transition appears legitimate. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): No material changes vs prior version; no suspicious additions; publisher has strong track record. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/workflow-tengo | AI (phantom-deps): Tengo workflow packages reference deps via config/build tooling, not direct JS imports; stable false positive for this package type. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.clonotype-enrichment.software | AI (phantom-deps): Same-org software dep referenced via build config, not direct import; expected pattern for this package family. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 2 / 2 | |
| 4.0.0 | 2 / 2 | |
| 3.2.1 | 2 / 2 | |
| 3.2.0 | 2 / 2 | |
| 3.1.2 | 2 / 2 | |
| 3.1.1 | 2 / 2 | |
| 3.1.0 | 2 / 2 | |
| 3.0.0 | 2 / 2 | |
| 2.22.4 | 2 / 2 | |
| 2.22.3 | 2 / 2 | |
| 2.22.2 | 2 / 2 |
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.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. 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.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. 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.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-13. 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.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-13. 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.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.