@sapui5/sap.ui.richtexteditor
SAPUI5 Library sap.ui.richtexteditor
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 | net-exec-file:src/sap/ui/richtexteditor/js/tiny_mce4/plugins/tinydrive/assetmanager.min.js | AI (source-diff): TinyDrive assetmanager is a legitimate TinyMCE commercial plugin; minified bundle with network calls is expected behavior. | ai | |
| source-diff | obfuscated-file:src/sap/ui/richtexteditor/js/tiny_mce4/plugins/advcode/customeditor.js | AI (source-diff): Ephox advanced code plugin — legitimate minified TinyMCE commercial plugin with clear copyright header. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large file count reflects bundling of TinyMCE 4 editor suite; expected for this SAP UI5 rich text editor package. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.150.0 | 0 / 0 | |
| 1.149.1 | 0 / 0 | |
| 1.149.0 | 0 / 0 | |
| 1.148.4 | 0 / 0 | |
| 1.148.3 | 0 / 0 | |
| 1.148.2 | 0 / 0 | |
| 1.148.1 | 0 / 0 | |
| 1.148.0 | 0 / 0 | |
| 1.147.1 | 0 / 0 | |
| 1.147.0 | 0 / 0 | |
| 1.146.0 | 0 / 0 | |
| 1.145.3 | 0 / 0 | |
| 1.145.2 | 0 / 0 | |
| 1.145.1 | 0 / 0 | |
| 1.145.0 | 0 / 0 | |
| 1.144.0 | 0 / 0 | |
| 1.143.1 | 0 / 0 | |
| 1.143.0 | 0 / 0 | |
| 1.142.10 | 0 / 0 | |
| 1.142.9 | 0 / 0 | |
| 1.142.8 | 0 / 0 | |
| 1.142.7 | 0 / 0 | |
| 1.142.6 | 0 / 0 | |
| 1.142.5 | 0 / 0 | |
| 1.142.4 | 0 / 0 | |
| 1.142.3 | 0 / 0 | |
| 1.142.2 | 0 / 0 | |
| 1.142.1 | 0 / 0 | |
| 1.136.18 | 0 / 0 | |
| 1.136.17 | 0 / 0 | |
| 1.136.16 | 0 / 0 | |
| 1.136.15 | 0 / 0 | |
| 1.136.14 | 0 / 0 | |
| 1.136.13 | 0 / 0 | |
| 1.136.12 | 0 / 0 | |
| 1.136.11 | 0 / 0 | |
| 1.136.9 | 0 / 0 | |
| 1.120.47 | 0 / 0 | |
| 1.120.46 | 0 / 0 | |
| 1.120.45 | 0 / 0 | |
| 1.120.44 | 0 / 0 | |
| 1.120.43 | 0 / 0 | |
| 1.120.42 | 0 / 0 | |
| 1.120.41 | 0 / 0 | |
| 1.120.40 | 0 / 0 | |
| 1.108.52 | 0 / 0 | |
| 1.108.51 | 0 / 0 | |
| 1.108.50 | 0 / 0 | |
| 1.108.49 | 0 / 0 | |
| 1.108.48 | 0 / 0 | |
| 1.108.47 | 0 / 0 | |
| 1.96.47 | 0 / 0 | |
| 1.96.46 | 0 / 0 | |
| 1.96.45 | 0 / 0 | |
| 1.96.44 | 0 / 0 | |
| 1.84.57 | 0 / 0 | |
| 1.84.56 | 0 / 0 | |
| 1.84.55 | 0 / 0 | |
| 1.84.54 | 0 / 0 |
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.148.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.146.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.144.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.143.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.143.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.47
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.