@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 — 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 | 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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.148.0 | 0 / 0 | |
| 1.147.1 | 0 / 0 | |
| 1.147.0 | 0 / 0 | |
| 1.145.3 | 0 / 0 | |
| 1.145.2 | 0 / 0 | |
| 1.145.1 | 0 / 0 | |
| 1.142.9 | 0 / 0 | |
| 1.142.8 | 0 / 0 | |
| 1.142.7 | 0 / 0 | |
| 1.136.16 | 0 / 0 | |
| 1.136.15 | 0 / 0 | |
| 1.120.45 | 0 / 0 | |
| 1.120.44 | 0 / 0 | |
| 1.120.43 | 0 / 0 | |
| 1.108.51 | 0 / 0 | |
| 1.108.50 | 0 / 0 | |
| 1.96.46 | 0 / 0 | |
| 1.96.45 | 0 / 0 | |
| 1.84.56 | 0 / 0 | |
| 1.84.55 | 0 / 0 |
v1.148.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.147.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.147.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.50
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.46
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.84.56
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.84.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.