@sapui5/sap.ushell — Greenflagged

SAPUI5 Library sap.ushell

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

sapnaassap_extncrepossap-ospo-admin

Keywords

sapui5ui5

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/Avatar.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/BusyIndicator.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/Button2.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/i18n-defaults.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/Link.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/List.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/ListItemCustom.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	obfuscated-file:src/main/js/sap/ushell/thirdparty/MenuItem2.js	AI (source-diff): SAP UI5 web component bundle; minified third-party assets are expected in this package.	ai	2026/05/13
source-diff	large-new-source-files	AI (source-diff): Large file counts are expected for SAP UI5 library packages with bundled web components.	ai	2026/05/13

Versions (showing 24 of 24)

Version	Deps	Published
1.148.1	0 / 2	2026-05-28
1.148.0	0 / 2	2026-05-14
1.147.2	0 / 2	2026-04-30
1.147.1	0 / 2	2026-04-21
1.147.0	0 / 2	2026-04-16
1.145.3	0 / 2	2026-05-27
1.145.2	0 / 2	2026-04-29
1.145.1	0 / 2	2026-04-03
1.142.11	0 / 2	2026-05-14
1.142.10	0 / 2	2026-04-23
1.142.9	0 / 2	2026-04-15
1.142.8	0 / 2	2026-04-03
1.136.19	0 / 2	2026-06-04
1.136.18	0 / 2	2026-05-13
1.136.17	0 / 2	2026-04-16
1.120.47	0 / 2	2026-05-29
1.120.46	0 / 2	2026-04-22
1.120.45	0 / 2	2026-04-08
1.108.54	0 / 1	2026-05-27
1.108.53	0 / 1	2026-04-22
1.96.48	0 / 1	2026-04-23
1.96.47	0 / 1	2026-04-01
1.84.54	0 / 1	2026-04-29
1.84.53	0 / 1	2026-04-08

v1.148.1

1 finding

LOW No provenance attestation provenance

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

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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

1 finding

LOW No provenance attestation provenance

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

v1.142.10

1 finding

LOW No provenance attestation provenance

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

v1.142.9

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

1 finding

LOW No provenance attestation provenance

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

v1.136.18

1 finding

LOW No provenance attestation provenance

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

v1.136.17

9 findings

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/Avatar.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.

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/BusyIndicator.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.

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/Button2.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.

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/i18n-defaults.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.

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/Link.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.

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/List.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.

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/ListItemCustom.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.

HIGH New obfuscated file: src/main/js/sap/ushell/thirdparty/MenuItem2.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.120.47

1 finding

LOW No provenance attestation provenance

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

v1.120.46

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.108.54

1 finding

LOW No provenance attestation provenance

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

v1.108.53

1 finding

LOW No provenance attestation provenance

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

v1.96.48

1 finding

LOW No provenance attestation provenance

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

v1.96.47

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

1 finding

LOW No provenance attestation provenance

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

v1.84.53

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.