@sapui5/sap.ushell_abap
SAPUI5 Library sap.ushell_abap
Supply chain provenance
Status for the latest visible version.
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
Keywords
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_abap/thirdparty/sap-xhrlib-esm.js | AI (source-diff): SAP-copyrighted minified XHR library bundle; standard distribution artifact for this SAP package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in a third-party SAP XHR library's internal module export helper; stable benign pattern for this package. | ai |
Versions (showing 100 of 190)
| Version | Deps | Published |
|---|---|---|
| 1.150.0 | 0 / 2 | |
| 1.149.1 | 0 / 2 | |
| 1.149.0 | 0 / 2 | |
| 1.148.4 | 0 / 2 | |
| 1.148.3 | 0 / 2 | |
| 1.148.2 | 0 / 2 | |
| 1.148.1 | 0 / 2 | |
| 1.148.0 | 0 / 2 | |
| 1.147.2 | 0 / 2 | |
| 1.147.1 | 0 / 2 | |
| 1.147.0 | 0 / 2 | |
| 1.146.0 | 0 / 2 | |
| 1.145.3 | 0 / 2 | |
| 1.145.2 | 0 / 2 | |
| 1.145.1 | 0 / 2 | |
| 1.145.0 | 0 / 2 | |
| 1.144.1 | 0 / 2 | |
| 1.144.0 | 0 / 2 | |
| 1.143.3 | 0 / 2 | |
| 1.143.2 | 0 / 2 | |
| 1.143.0 | 0 / 2 | |
| 1.142.12 | 0 / 2 | |
| 1.142.11 | 0 / 2 | |
| 1.142.10 | 0 / 2 | |
| 1.142.9 | 0 / 2 | |
| 1.142.8 | 0 / 2 | |
| 1.142.7 | 0 / 2 | |
| 1.142.6 | 0 / 2 | |
| 1.142.5 | 0 / 2 | |
| 1.142.4 | 0 / 2 | |
| 1.142.3 | 0 / 2 | |
| 1.142.1 | 0 / 2 | |
| 1.142.0 | 0 / 2 | |
| 1.141.3 | 0 / 2 | |
| 1.141.2 | 0 / 2 | |
| 1.141.1 | 0 / 2 | |
| 1.141.0 | 0 / 2 | |
| 1.140.0 | 0 / 2 | |
| 1.139.5 | 0 / 2 | |
| 1.139.4 | 0 / 2 | |
| 1.139.2 | 0 / 2 | |
| 1.139.1 | 0 / 2 | |
| 1.139.0 | 0 / 2 | |
| 1.138.1 | 0 / 2 | |
| 1.138.0 | 0 / 2 | |
| 1.136.20 | 0 / 2 | |
| 1.136.19 | 0 / 2 | |
| 1.136.18 | 0 / 2 | |
| 1.136.17 | 0 / 2 | |
| 1.136.16 | 0 / 2 | |
| 1.136.15 | 0 / 2 | |
| 1.136.14 | 0 / 2 | |
| 1.136.12 | 0 / 2 | |
| 1.136.11 | 0 / 2 | |
| 1.136.10 | 0 / 2 | |
| 1.136.9 | 0 / 2 | |
| 1.136.8 | 0 / 2 | |
| 1.136.7 | 0 / 2 | |
| 1.136.6 | 0 / 2 | |
| 1.136.5 | 0 / 2 | |
| 1.136.4 | 0 / 2 | |
| 1.136.3 | 0 / 2 | |
| 1.136.2 | 0 / 2 | |
| 1.136.1 | 0 / 2 | |
| 1.136.0 | 0 / 2 | |
| 1.135.0 | 0 / 2 | |
| 1.134.1 | 0 / 2 | |
| 1.134.0 | 0 / 2 | |
| 1.133.3 | 0 / 2 | |
| 1.133.2 | 0 / 2 | |
| 1.133.1 | 0 / 2 | |
| 1.133.0 | 0 / 2 | |
| 1.132.1 | 0 / 2 | |
| 1.132.0 | 0 / 2 | |
| 1.131.1 | 0 / 2 | |
| 1.131.0 | 0 / 2 | |
| 1.130.9 | 0 / 2 | |
| 1.130.8 | 0 / 2 | |
| 1.130.7 | 0 / 2 | |
| 1.130.6 | 0 / 2 | |
| 1.130.5 | 0 / 2 | |
| 1.130.4 | 0 / 2 | |
| 1.130.3 | 0 / 2 | |
| 1.130.2 | 0 / 2 | |
| 1.130.1 | 0 / 2 | |
| 1.130.0 | 0 / 2 | |
| 1.129.1 | 0 / 2 | |
| 1.129.0 | 0 / 2 | |
| 1.128.1 | 0 / 2 | |
| 1.128.0 | 0 / 2 | |
| 1.127.7 | 0 / 2 | |
| 1.127.6 | 0 / 2 | |
| 1.127.5 | 0 / 2 | |
| 1.127.4 | 0 / 2 | |
| 1.127.3 | 0 / 2 | |
| 1.127.2 | 0 / 2 | |
| 1.127.1 | 0 / 2 | |
| 1.127.0 | 0 / 2 | |
| 1.126.1 | 0 / 2 | |
| 1.126.0 | 0 / 2 |
v1.150.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.149.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.148.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.148.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.135.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.134.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.134.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.133.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.133.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.132.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.132.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.131.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.131.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.129.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.129.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.128.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.128.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.126.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.126.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.