← Home

ml-array-mean

npm Repository Homepage

Get the average value in an array

11
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

stropitektargoslpatinymljs-botmaasencioh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition within the mljs org; lpatiny is a long-standing trusted publisher of mljs packages. ai

Versions (showing 11 of 11)

Version Deps Published
2.0.0 1 / 0
1.1.6 1 / 0
1.1.5 1 / 0
1.1.4 1 / 0
1.1.3 1 / 0
1.1.2 1 / 0
1.1.1 1 / 0
1.1.0 1 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v2.0.0

2 findings
HIGH Publisher changed: targos → mljs-bot (on 2026-04-14) provenance

This version was published by a different npm account than previous versions on 2026-04-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lpatiny → targos (on 2020-10-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-07. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.3

2 findings
HIGH Publisher changed: stropitek → lpatiny (on 2020-04-17) provenance

This version was published by a different npm account than previous versions on 2020-04-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

2 findings
HIGH Publisher changed: stropitek → lpatiny (on 2019-08-30) provenance

This version was published by a different npm account than previous versions on 2019-08-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lpatiny → stropitek (on 2018-11-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-09. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

2 findings
HIGH Publisher changed: maasencioh → lpatiny (on 2018-08-03) provenance

This version was published by a different npm account than previous versions on 2018-08-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.