@openui5/sap.ui.support Apache-2.0 51 versions

@openui5/sap.ui.support

npm Repository

OpenUI5 UI Library sap.ui.support

51

Versions

Apache-2.0

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

sap-ospo-adminopenui5-bot

Keywords

openui5sapui5ui5

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:eval-usage	AI (semgrep): eval() used only as a CSP capability probe (eval("") in try/catch), not for executing untrusted input. Stable pattern for this package.	ai	2026/05/27
phantom-deps	phantom-dep:@openui5/sap.m	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic doesn't apply to UI5 module system.	ai	2026/04/30
phantom-deps	phantom-dep:@openui5/sap.ui.fl	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic doesn't apply to UI5 module system.	ai	2026/04/30
semgrep	semgrep:new-function-constructor	AI (semgrep): Used only as a CSP/eval-allowed probe (new Function("") in try/catch); not executing user input.	ai	2026/04/30
phantom-deps	phantom-dep:@openui5/sap.ui.layout	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic doesn't apply to UI5 module system.	ai	2026/04/30
phantom-deps	phantom-dep:@openui5/sap.ui.codeeditor	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic doesn't apply to UI5 module system.	ai	2026/04/30
phantom-deps	phantom-dep:@openui5/sap.ui.core	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic doesn't apply to UI5 module system.	ai	2026/04/30

Versions (showing 51 of 98)

View all versions

Version	Deps	Published
1.148.0	5 / 0	2026-05-12
1.147.1	5 / 0	2026-04-21
1.147.0	5 / 0	2026-04-15
1.146.0	5 / 0	2026-03-16
1.145.3	5 / 0	2026-05-27
1.145.2	5 / 0	2026-04-28
1.145.1	5 / 0	2026-03-30
1.145.0	5 / 0	2026-02-16
1.144.0	5 / 0	2026-01-22
1.143.1	5 / 0	2025-12-11
1.143.0	5 / 0	2025-11-25
1.142.9	5 / 0	2026-05-11
1.142.8	5 / 0	2026-04-15
1.142.7	5 / 0	2026-03-30
1.142.6	5 / 0	2026-03-10
1.142.5	5 / 0	2026-02-09
1.142.4	5 / 0	2026-02-05
1.142.3	5 / 0	2026-01-26
1.142.2	5 / 0	2026-01-05
1.142.1	5 / 0	2025-12-10
1.142.0	5 / 0	2025-10-30
1.141.2	5 / 0	2025-10-22
1.141.1	5 / 0	2025-10-09
1.141.0	5 / 0	2025-09-30
1.140.0	5 / 0	2025-09-01
1.139.3	5 / 0	2025-12-10
1.139.2	5 / 0	2025-10-27
1.139.1	5 / 0	2025-10-07
1.139.0	5 / 0	2025-08-06
1.138.0	5 / 0	2025-07-07
1.136.17	5 / 0	2026-06-03
1.136.16	5 / 0	2026-05-11
1.136.15	5 / 0	2026-04-16
1.136.14	5 / 0	2026-03-24
1.136.13	5 / 0	2026-02-23
1.136.12	5 / 0	2026-01-13
1.136.11	5 / 0	2025-12-18
1.136.10	5 / 0	2025-12-18
1.136.9	5 / 0	2025-11-24
1.136.8	5 / 0	2025-10-28
1.136.7	5 / 0	2025-10-01
1.136.6	5 / 0	2025-09-03
1.136.5	5 / 0	2025-08-19
1.136.4	5 / 0	2025-08-11
1.136.3	5 / 0	2025-07-28
1.136.2	5 / 0	2025-07-08
1.136.1	5 / 0	2025-06-16
1.136.0	5 / 0	2025-05-14
1.133.3	5 / 0	2025-06-23
1.130.8	5 / 0	2025-06-03
1.120.45	5 / 0	2026-05-18

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.146.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.145.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.144.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.143.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.143.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.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.142.6

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

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

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

v1.136.14

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

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

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

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

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.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.136.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.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.6

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

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

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.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.136.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.136.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.136.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.133.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.130.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.120.45

1 finding

LOW No provenance attestation provenance

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