@openui5/sap.ui.core — Greenflagged

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

sap-ospo-adminopenui5-bot

Keywords

openui5sapui5ui5

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:src/sap/ui/thirdparty/unormdata.js	AI (source-diff): Long lines are compact Unicode normalization data tables, not obfuscated malware.	ai	2026/05/12
source-diff	net-exec-file:src/sap/ui/thirdparty/es6-shim-nopromise.js	AI (source-diff): Well-known es6-shim polyfill with MIT license; SAP-modified UMD wrapper, not malware.	ai	2026/05/12
source-diff	net-exec-file:src/sap/ui/thirdparty/flexie.js	AI (source-diff): Flexie CSS3 flexbox polyfill with MIT license; legitimate third-party library.	ai	2026/05/12
source-diff	net-exec-file:src/sap/base/strings/NormalizePolyfill.js	AI (source-diff): SAP OpenUI5 Unicode normalization polyfill with Apache-2.0 header; not malware.	ai	2026/05/12
source-diff	net-exec-file:src/sap/ui/thirdparty/es6-promise.js	AI (source-diff): Well-known es6-promise polyfill with MIT license header; SAP-modified UMD wrapper, not malware.	ai	2026/05/12
source-diff	net-exec-file:src/sap/ui/core/plugin/LessSupport.js	AI (source-diff): LessSupport.js is a documented SAP dev-only LESS plugin; network+eval pattern is intentional and not malicious.	ai	2026/05/12
semgrep	semgrep:new-function-constructor	AI (semgrep): new Function() in syncXHRFix legacy event handler path; documented legacy-relevant pattern in UI5 codebase.	ai	2026/04/30
semgrep	semgrep:eval-usage	AI (semgrep): Legacy eval usage in jQuery.sap.global compatibility shim; stable pattern across all UI5 versions.	ai	2026/04/30

Versions (showing 22 of 22)

Version	Deps	Published
1.148.0	0 / 0	2026-05-12
1.147.1	0 / 0	2026-04-21
1.147.0	0 / 0	2026-04-15
1.145.3	0 / 0	2026-05-27
1.145.2	0 / 0	2026-04-28
1.145.1	0 / 0	2026-03-30
1.142.9	0 / 0	2026-05-11
1.142.8	0 / 0	2026-04-15
1.142.7	0 / 0	2026-03-30
1.136.17	0 / 0	2026-06-03
1.136.16	0 / 0	2026-05-11
1.136.15	0 / 0	2026-04-16
1.120.45	0 / 0	2026-05-18
1.120.44	0 / 0	2026-04-20
1.120.43	0 / 0	2026-04-06
1.108.51	0 / 0	2026-05-27
1.108.50	0 / 0	2026-04-21
1.96.46	0 / 0	2026-04-21
1.96.45	0 / 0	2026-04-01
1.84.56	0 / 0	2026-04-29
1.84.55	0 / 0	2026-04-07
1.71.78	0 / 0	2026-05-04

v1.148.0

1 finding

LOW No provenance attestation provenance

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

v1.147.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.145.3

1 finding

LOW No provenance attestation provenance

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

v1.145.2

1 finding

LOW No provenance attestation provenance

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

v1.145.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.142.9

1 finding

LOW No provenance attestation provenance

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

v1.142.8

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.142.7

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.136.17

1 finding

LOW No provenance attestation provenance

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

v1.136.16

1 finding

LOW No provenance attestation provenance

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

v1.136.15

1 finding

LOW No provenance attestation provenance

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

v1.120.45

1 finding

LOW No provenance attestation provenance

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

v1.120.44

1 finding

LOW No provenance attestation provenance

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

v1.120.43

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.108.51

1 finding

LOW No provenance attestation provenance

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

v1.108.50

1 finding

LOW No provenance attestation provenance

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

v1.96.46

2 findings

HIGH New file with network + code execution: src/sap/ui/core/plugin/LessSupport.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.96.45

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.84.56

7 findings

HIGH New file with network + code execution: src/sap/ui/thirdparty/es6-promise.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: src/sap/ui/thirdparty/es6-shim-nopromise.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: src/sap/ui/thirdparty/flexie.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: src/sap/ui/core/plugin/LessSupport.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: src/sap/base/strings/NormalizePolyfill.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: src/sap/ui/thirdparty/unormdata.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.84.55

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.71.78

1 finding

LOW No provenance attestation provenance

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