@platforma-open/milaboratories.clonotype-clustering.software
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Platforma SDK packages consistently lack descriptions/keywords/repo URLs; stable false positive for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): No-description is a consistent pattern across this Platforma SDK package family, not a malice indicator. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 0 / 2 | |
| 3.11.2 | 0 / 2 | |
| 3.11.1 | 0 / 2 | |
| 3.11.0 | 0 / 2 | |
| 3.10.0 | 0 / 2 | |
| 3.9.8 | 0 / 2 |
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.11.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.11.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.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.