ml-tree-similarity
Compares two spectra using a tree similarity
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): mljs-bot is the mljs org's publishing bot (39 approved, 0 rejected, 1856 days old). Transition from targos to mljs-bot is a legitimate org workflow change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mljs-bot is the established publishing bot for the mljs organization; addition is a legitimate org workflow transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of jeffersonh44 concurrent with mljs-bot addition reflects org consolidation to bot publishing. | ai | |
| phantom-deps | phantom-dep:cheminfo-types | AI (phantom-deps): cheminfo-types provides TypeScript types used via type annotations, not direct imports; phantom detection is expected. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 2 / 9 | |
| 2.1.0 | 2 / 7 | |
| 2.0.0 | 3 / 7 | |
| 1.0.0 | 2 / 7 | |
| 0.1.0 | 2 / 8 | |
| 0.0.0 | 0 / 3 |
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2024-02-09. 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.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-29. This could indicate a legitimate maintainer transition or an account compromise.