ml-matrix No license 34 versions

ml-matrix

npm Repository Homepage

34

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

stropitektargoslpatinymljs-botmaasenciohjeffersonh44andcastillo

Keywords

matrixdecompositionSVDsingularvalueEVDeigenvalueLUQrCholeskydataminingdataminingmachinelearning

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established mljs ecosystem package with clean history; lack of provenance attestation is not a security concern for this package.	ai	2026/04/26

Versions (showing 34 of 34)

Version	Deps	Published
6.14.0	2 / 19	2026-07-13
6.13.0	2 / 18	2026-06-23
6.12.2	2 / 17	2026-04-16
6.12.1	2 / 17	2025-03-11
6.12.0	2 / 17	2024-10-15
6.11.1	2 / 17	2024-06-10
6.11.0	2 / 17	2023-11-30
6.10.8	2 / 17	2023-11-04
6.10.7	2 / 17	2023-10-20
6.10.6	2 / 17	2023-10-17
6.10.5	2 / 17	2023-09-24
6.10.4	2 / 16	2022-11-05
6.10.3	2 / 16	2022-11-04
6.10.2	2 / 16	2022-06-29
6.10.1	2 / 16	2022-05-31
6.10.0	2 / 16	2022-04-19
6.9.0	2 / 16	2022-02-26
6.8.2	1 / 16	2021-11-12
6.8.1	1 / 16	2021-11-04
6.8.0	1 / 16	2021-04-23
6.7.0	1 / 16	2021-03-12
6.6.0	1 / 16	2021-01-04
6.5.3	1 / 16	2020-10-11
6.5.2	1 / 18	2020-10-09
6.5.1	1 / 21	2020-07-28
6.5.0	1 / 20	2020-05-03
6.4.1	1 / 20	2019-09-30
6.4.0	1 / 20	2019-08-16
6.3.0	1 / 20	2019-08-16
6.2.0	1 / 15	2019-07-20
6.1.2	1 / 14	2019-06-29
6.1.1	1 / 14	2019-06-28
6.1.0	1 / 13	2019-06-22
6.0.0	1 / 13	2019-04-25

v6.14.0

1 finding

INFO No provenance attestation provenance

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

v6.12.1

1 finding

INFO No provenance attestation provenance

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

v6.12.0

1 finding

INFO No provenance attestation provenance

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

v6.11.1

1 finding

INFO No provenance attestation provenance

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

v6.11.0

1 finding

INFO No provenance attestation provenance

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

v6.10.7

1 finding

INFO No provenance attestation provenance

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

v6.10.6

1 finding

INFO No provenance attestation provenance

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

v6.10.5

1 finding

INFO No provenance attestation provenance

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

v6.10.4

1 finding

INFO No provenance attestation provenance

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

v6.10.3

1 finding

INFO No provenance attestation provenance

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

v6.10.2

1 finding

INFO No provenance attestation provenance

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

v6.10.1

1 finding

INFO No provenance attestation provenance

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

v6.10.0

1 finding

INFO No provenance attestation provenance

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

v6.9.0

1 finding

INFO No provenance attestation provenance

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

v6.8.2

1 finding

INFO No provenance attestation provenance

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

v6.8.1

1 finding

INFO No provenance attestation provenance

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

v6.8.0

1 finding

INFO No provenance attestation provenance

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

v6.7.0

2 findings

MEDIUM Publisher changed: zakodium-bot → mljs-bot (on 2021-03-12, unremoved on npm for 1957d) provenance

This version was published by a different npm account (mljs-bot) than the most recent previously approved version (zakodium-bot) on 2021-03-12. It has since remained available on npm for 1957 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

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

v6.6.0

2 findings

MEDIUM Publisher changed: zakodium-bot → mljs-bot (on 2021-01-04, unremoved on npm for 2023d) provenance

This version was published by a different npm account (mljs-bot) than the most recent previously approved version (zakodium-bot) on 2021-01-04. It has since remained available on npm for 2023 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

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

v6.5.3

2 findings

MEDIUM Publisher changed: targos → zakodium-bot (on 2020-10-11, unremoved on npm for 2109d) provenance

This version was published by a different npm account (zakodium-bot) than the most recent previously approved version (targos) on 2020-10-11. It has since remained available on npm for 2109 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

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

v6.5.2

1 finding

INFO No provenance attestation provenance

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

v6.5.1

1 finding

INFO No provenance attestation provenance

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

v6.5.0

1 finding

INFO No provenance attestation provenance

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

v6.4.1

1 finding

INFO No provenance attestation provenance

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

v6.4.0

1 finding

INFO No provenance attestation provenance

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

v6.3.0

1 finding

INFO No provenance attestation provenance

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

v6.2.0

1 finding

INFO No provenance attestation provenance

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

v6.1.2

1 finding

INFO No provenance attestation provenance

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

v6.1.1

1 finding

INFO No provenance attestation provenance

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

v6.1.0

1 finding

INFO No provenance attestation provenance

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

v6.0.0

1 finding

INFO No provenance attestation provenance

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