@openui5/sap.ui.support
OpenUI5 UI Library sap.ui.support
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 |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 7 of 207)
| Version | Deps | Published |
|---|---|---|
| 1.71.71 | 6 / 0 | |
| 1.71.70 | 6 / 0 | |
| 1.71.69 | 6 / 0 | |
| 1.71.68 | 6 / 0 | |
| 1.71.67 | 6 / 0 | |
| 1.71.66 | 6 / 0 | |
| 1.71.65 | 6 / 0 |
v1.71.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.