ml-distance
Distance and similarity functions to compare vectors
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): targos (Michaël Zasso) to mljs-bot is a known mljs org bot migration; both are established mljs maintainers. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mljs-bot is the mljs org's automation account (38 approved, 0 rejected); legitimate org-level transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): ml-bot replaced by mljs-bot — same org bot account renamed/migrated. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 3 / 11 | |
| 4.0.0 | 3 / 11 | |
| 3.0.0 | 3 / 7 | |
| 2.1.1 | 3 / 3 | |
| 2.1.0 | 3 / 3 | |
| 2.0.1 | 2 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.0.2 | 0 / 16 | |
| 1.0.1 | 0 / 16 | |
| 1.0.0 | 0 / 3 |
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-01-06. 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.