@openui5/sap.ui.webc.common
OpenUI5 UI Library sap.ui.webc.common
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@openui5/sap.ui.core | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic is a stable false positive for this monorepo-style package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.146.0 | 1 / 0 | |
| 1.145.3 | 1 / 0 | |
| 1.145.2 | 1 / 0 | |
| 1.145.1 | 1 / 0 | |
| 1.142.9 | 1 / 0 | |
| 1.142.8 | 1 / 0 | |
| 1.142.7 | 1 / 0 | |
| 1.136.17 | 1 / 0 | |
| 1.136.16 | 1 / 0 | |
| 1.136.15 | 1 / 0 | |
| 1.120.45 | 1 / 0 | |
| 1.120.44 | 1 / 0 | |
| 1.120.43 | 1 / 0 | |
| 1.108.50 | 1 / 0 | |
| 1.96.46 | 1 / 0 | |
| 1.96.45 | 1 / 0 | |
| 1.96.44 | 1 / 0 | |
| 1.96.43 | 1 / 0 | |
| 1.96.42 | 1 / 0 | |
| 1.96.41 | 1 / 0 | |
| 1.96.40 | 1 / 0 | |
| 1.96.39 | 1 / 0 |
v1.145.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.2
1 findingPackage 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
1 findingPackage 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
1 findingPackage 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.50
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.