ml-stat
Functions for computing stats on arrays and matrices
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): Publisher change from stropitek to targos occurred in 2015. targos (Michaël Zasso) is a well-known Node.js core contributor listed in package.json contributors; transition is legitimate and historical. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer addition of targos is a decade-old, legitimate transition. targos has 55 approved packages and a clean track record; no ongoing risk. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance infrastructure by many years; absence of attestation is expected and not a risk signal for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.3.3 | 0 / 6 | |
| 1.3.2 | 0 / 6 | |
| 1.3.1 | 0 / 6 | |
| 1.3.0 | 0 / 6 | |
| 1.2.0 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.1 | 0 / 3 | |
| 1.0.0 | 0 / 3 |
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
2 findings[Accepted risk] Package 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 2016-09-02. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findings[Accepted risk] Package 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 2016-08-05. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2015-02-02. 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
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.