onnxruntime-common MIT 40 versions

onnxruntime-common

npm Repository Homepage

ONNXRuntime JavaScript API library

40

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

erscorerscor_msfteirezuzhao

Keywords

ONNXONNXRuntimeONNX Runtime

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition from personal account 'eire' (fs-eire) to org account 'onnxruntime' — both long-standing Microsoft ONNX Runtime maintainers. Legitimate handoff.	ai	2026/04/23
publish-pattern	suspicious-version-number	AI (publish-pattern): Dev/nightly prerelease versioning with date+commit hash is standard for onnxruntime-common builds.	ai	2026/04/23
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Standard Proxy handler using Reflect.get() — idiomatic JS pattern, not obfuscation. Stable for this package.	ai	2026/04/21

Versions (showing 40 of 40)

Hide prereleases

Version	Deps	Published
1.26.0	0 / 2	2026-05-08
1.25.1	0 / 2	2026-04-29
1.24.3	0 / 2	2026-03-05
1.24.2	0 / 2	2026-02-19
1.24.1	0 / 2	2026-02-05
1.23.2	0 / 1	2025-11-04
1.23.0	0 / 1	2025-09-26
1.22.0	0 / 1	2025-05-09
1.21.1	0 / 1	2025-04-21
1.21.0	0 / 1	2025-03-08
1.20.1	0 / 1	2024-11-22
1.20.0	0 / 1	2024-10-31
1.19.2	0 / 1	2024-09-03
1.19.0	0 / 1	2024-08-15
1.18.0	0 / 1	2024-05-17
1.17.3	0 / 1	2024-04-11
1.17.1	0 / 1	2024-02-25
1.17.0	0 / 1	2024-01-31
1.16.3	0 / 1	2023-11-20
1.16.2	0 / 1	2023-11-09
1.16.1	0 / 1	2023-10-11
1.16.0	0 / 1	2023-09-19
1.15.1	0 / 1	2023-06-17
1.15.0	0 / 1	2023-05-24
1.14.0	0 / 5	2023-02-10
1.13.1	0 / 5	2022-10-24
1.12.1	0 / 5	2022-08-04
1.12.0	0 / 5	2022-07-22
1.11.0	0 / 5	2022-03-25
1.10.0	0 / 5	2021-12-07
1.9.0	0 / 4	2021-09-22
1.8.0	0 / 4	2021-06-03
1.24.0-dev.20251116-b39e144322	0 / 2	2025-11-17
1.24.0-dev.20251104-75d35474d5	0 / 2	2025-11-05
1.23.0-dev.20250703-7fc6235861	0 / 1	2025-07-03
1.23.0-dev.20250612-70f14d7670	0 / 1	2025-06-12
1.23.0-dev.20250515-00bd398d54	0 / 1	2025-05-16
1.23.0-dev.20250429-a9a3ad2e0c	0 / 1	2025-05-02
1.22.0-rc.20250421-2abab8d39e	0 / 1	2025-04-21
1.22.0-dev.20250504-93f85fb7b2	0 / 1	2025-05-09

v1.26.0

1 finding

LOW No provenance attestation provenance

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

v1.25.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: onnxruntime → erscor (on 2026-04-29) provenance

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

v1.24.3

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.

v1.24.2

1 finding

LOW No provenance attestation provenance

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

v1.24.1

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.

v1.23.2

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.

v1.23.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.

v1.22.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.

v1.21.1

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.

v1.21.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.

v1.20.1

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.

v1.20.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.

v1.19.2

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.

v1.19.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.

v1.18.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.

v1.17.3

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.

v1.17.1

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.

v1.17.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.

v1.16.3

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.

v1.16.2

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.

v1.16.1

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.

v1.16.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.

v1.15.1

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.

v1.15.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.

v1.14.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.

v1.13.1

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.

v1.12.1

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.

v1.12.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.

v1.11.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.

v1.10.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.

v1.9.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.

v1.8.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.

v1.24.0-dev.20251116-b39e144322

2 findings

HIGH Publisher changed: onnxruntime → eire (on 2025-11-17) provenance

This version was published by a different npm account than previous versions on 2025-11-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.24.0-dev.20251104-75d35474d5

2 findings

HIGH Publisher changed: onnxruntime → eire (on 2025-11-05) provenance

This version was published by a different npm account than previous versions on 2025-11-05. 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.23.0-dev.20250703-7fc6235861

1 finding

LOW No provenance attestation provenance

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

v1.23.0-dev.20250612-70f14d7670

2 findings

HIGH Publisher changed: onnxruntime → eire (on 2025-06-12) provenance

This version was published by a different npm account than previous versions on 2025-06-12. 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.23.0-dev.20250515-00bd398d54

2 findings

HIGH Publisher changed: onnxruntime → eire (on 2025-05-16) provenance

This version was published by a different npm account than previous versions on 2025-05-16. 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.23.0-dev.20250429-a9a3ad2e0c

1 finding

LOW No provenance attestation provenance

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

v1.22.0-rc.20250421-2abab8d39e

2 findings

HIGH Publisher changed: eire → onnxruntime (on 2025-04-21) provenance

This version was published by a different npm account than previous versions on 2025-04-21. 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.22.0-dev.20250504-93f85fb7b2

2 findings

HIGH Publisher changed: eire → onnxruntime (on 2025-05-09) provenance

This version was published by a different npm account than previous versions on 2025-05-09. 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.