@openui5/sap.ui.webc.main
Supply chain provenance
Status for the latest visible version.
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
Keywords
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/webc/main/thirdparty/generated/assets/themes/sap_horizon_hcw_exp/parameters-bundle.css.json.js | AI (source-diff): Minified CSS-in-JS theme asset bundle; standard SAP UI5 build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/themes/sap_horizon_hcb_exp/parameters-bundle.css.js | AI (source-diff): Minified CSS-in-JS theme bundle; standard SAP UI5 build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/themes/sap_horizon_hcb_exp/parameters-bundle.css.json.js | AI (source-diff): Minified CSS-in-JS theme asset bundle; standard SAP UI5 build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/themes/sap_horizon_dark_exp/parameters-bundle.css.json.js | AI (source-diff): Minified CSS-in-JS theme asset bundle; standard SAP UI5 build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/themes/sap_horizon_hcw_exp/parameters-bundle.css.js | AI (source-diff): Minified CSS-in-JS theme bundle; standard SAP UI5 build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/themes/sap_horizon_dark_exp/parameters-bundle.css.js | AI (source-diff): Minified CSS-in-JS theme bundle; standard SAP UI5 build artifact, not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_en_US_sappsd.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_en_US_saprigi.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 144 new files are localization bundles for additional languages; expected for SAP UI5 i18n expansion. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_en_GB.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_cs.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_cy.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_da.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_de.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_el.json.js | AI (source-diff): Minified i18n translation bundle; benign SAP build artifact. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_ca.json.js | AI (source-diff): Same pattern: minified i18n translation bundle, not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_bg.json.js | AI (source-diff): Same pattern: minified i18n translation bundle, not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:src/sap/ui/webc/main/thirdparty/generated/assets/i18n/messagebundle_ar.json.js | AI (source-diff): Minified i18n translation bundle; long lines are JSON key-value pairs, not obfuscated malicious code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@openui5/sap.ui.core | AI (phantom-deps): UI5 framework loads modules at runtime; same-org dep not directly imported is expected pattern. | ai | |
| phantom-deps | phantom-dep:@openui5/sap.ui.webc.common | AI (phantom-deps): UI5 framework loads modules at runtime; same-org dep not directly imported is expected pattern. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.146.0 | 2 / 0 | |
| 1.145.3 | 2 / 0 | |
| 1.145.2 | 2 / 0 | |
| 1.145.1 | 2 / 0 | |
| 1.142.9 | 2 / 0 | |
| 1.142.8 | 2 / 0 | |
| 1.142.7 | 2 / 0 | |
| 1.136.17 | 2 / 0 | |
| 1.136.16 | 2 / 0 | |
| 1.136.15 | 2 / 0 | |
| 1.120.45 | 2 / 0 | |
| 1.120.44 | 2 / 0 | |
| 1.120.43 | 2 / 0 | |
| 1.108.51 | 2 / 0 | |
| 1.108.50 | 2 / 0 | |
| 1.96.47 | 2 / 0 | |
| 1.96.46 | 2 / 0 | |
| 1.96.45 | 2 / 0 | |
| 1.96.44 | 2 / 0 | |
| 1.96.43 | 2 / 0 | |
| 1.96.42 | 2 / 0 | |
| 1.96.41 | 2 / 0 | |
| 1.96.40 | 2 / 0 | |
| 1.96.39 | 2 / 0 |
v1.145.3
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.8
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.15
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.44
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.43
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.50
12 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.