diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index c67458f2de7d2f6340c893e36bb1fb417b84af19..f3a94c255ae9f2591d1d778b6f45d2f7405e4c33 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -14,7 +14,7 @@ body:
     attributes:
       label: How are you running Renovate?
       options:
-        - 'WhiteSource Renovate hosted app on github.com'
+        - 'Mend Renovate hosted app on github.com'
         - 'Self-hosted'
     validations:
       required: true
diff --git a/.github/label-actions.yml b/.github/label-actions.yml
index c74b345b724cf26a07062d3ac5476ed98c6727b0..4a70d8c83e346e30f5286d23606fbb11240aae3e 100644
--- a/.github/label-actions.yml
+++ b/.github/label-actions.yml
@@ -46,7 +46,7 @@
 
     1. Go to the affected PR, and search for "View repository job log here"
 
-    1. Click on the link to go to the "WhiteSource Renovate Dashboard" and log in
+    1. Click on the link to go to the "Mend Renovate Dashboard" and log in
 
     1. You are now in the correct repository log overview screen
 
diff --git a/docs/usage/assets/images/logo.png b/docs/usage/assets/images/logo.png
index 42b58222ca419af99260afb0125c28e12829a009..a3a15bb491e4cb8421cbee9ff274f2f5cc34cbd7 100644
Binary files a/docs/usage/assets/images/logo.png and b/docs/usage/assets/images/logo.png differ
diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md
index 120c845f10ce08d64ef39dcaf178c42b2efb8dc7..d8d58c26b09f6e86011f0bdea9bc94c71c200023 100644
--- a/docs/usage/configuration-options.md
+++ b/docs/usage/configuration-options.md
@@ -1240,7 +1240,7 @@ By default, Renovate will skip over any repositories that are forked.
 This includes if the forked repository has a Renovate config file, because Renovate can't tell if that file was added by the original repository or not.
 If you wish to enable processing of a forked repository by Renovate, you need to add `"includeForks": true` to your repository config or run the CLI command with `--include-forks=true`.
 
-If you are using the hosted WhiteSource Renovate then this option will be configured to `true` automatically if you "Selected" repositories individually but remain as `false` if you installed for "All" repositories.
+If you are using the hosted Mend Renovate then this option will be configured to `true` automatically if you "Selected" repositories individually but remain as `false` if you installed for "All" repositories.
 
 ## includePaths
 
diff --git a/docs/usage/getting-started/installing-onboarding.md b/docs/usage/getting-started/installing-onboarding.md
index 4e3f9422578d97913c974485c6b8f3096cacebf5..9cc5b3e7ee8417ff6bb5cf6874e94aa3e6acdc21 100644
--- a/docs/usage/getting-started/installing-onboarding.md
+++ b/docs/usage/getting-started/installing-onboarding.md
@@ -9,11 +9,11 @@ If the administrator has configured a fixed list of repositories then the only w
 Otherwise, the process for adding new repositories to a Renovate installation can vary:
 
 - Most commonly, you run Renovate as a dedicated "bot user" with global config option `autodiscover` set to `true`, meaning that it will run on every repository which it's been granted access to
-- If using a GitHub App (including WhiteSource Renovate on `github.com`) then you can install the app into a user or organization account and select either "All repositories", or "Select repositories" and pick them manually
+- If using a GitHub App (including Mend Renovate on `github.com`) then you can install the app into a user or organization account and select either "All repositories", or "Select repositories" and pick them manually
 
 ### Hosted GitHub.com App
 
-Installing/enabling WhiteSource's Renovate GitHub App is simple.
+Installing/enabling Mend's Renovate GitHub App is simple.
 
 First, navigate to [https://github.com/apps/renovate](https://github.com/apps/renovate) and click the Install button:
 
@@ -31,12 +31,12 @@ Once you're done selecting repositories for Renovate to run on, click the green
 
 <!-- prettier-ignore -->
 !!! note
-    If you are using the WhiteSource Renovate App then it has a custom behavior for forked repositories.
+    If you are using the Mend Renovate App then it has a custom behavior for forked repositories.
     If you choose "All repositories" when installing then forked repositories will be skipped by default, while if you choose "Select repositories" then they will be processed by Renovate even if they're a fork.
 
 ### Hosted GitLab.com App
 
-Unfortunately WhiteSource's hosted GitLab app needed to be taken offline indefinitely until a viable security model for bots on GitLab.com is available.
+Unfortunately Mend's hosted GitLab app needed to be taken offline indefinitely until a viable security model for bots on GitLab.com is available.
 For more details on GitLab security for bots, please see the [GitLab Bot Security](../gitlab-bot-security.md) doc.
 
 ## Repository onboarding
@@ -137,4 +137,4 @@ Any existing Renovate PRs will be closed after you've completed these steps.
 1. Remove the current Renovate configuration file (e.g. `renovate.json`) from your mainline branch
 
 Following these steps will trick Renovate into thinking that your repository was _never_ onboarded, and will trigger a new "Configure Renovate" PR.
-If you're using the hosted WhiteSource Renovate App and you don't get a new onboarding PR within a few hours, then please create a Discussions post to request staff trigger it manually.
+If you're using the hosted Mend Renovate App and you don't get a new onboarding PR within a few hours, then please create a Discussions post to request staff trigger it manually.
diff --git a/docs/usage/getting-started/private-packages.md b/docs/usage/getting-started/private-packages.md
index 3a3072fb452551d8daa38b0a166bb586c3c1a63a..46586c41ba484044ecfa54520e1dafad1c51f249 100644
--- a/docs/usage/getting-started/private-packages.md
+++ b/docs/usage/getting-started/private-packages.md
@@ -356,9 +356,9 @@ module.exports = {
 };
 ```
 
-## WhiteSource Renovate Hosted App Encryption
+## Mend Renovate Hosted App Encryption
 
-The popular [Renovate App on GitHub](https://github.com/apps/renovate) is hosted by WhiteSource.
+The popular [Renovate App on GitHub](https://github.com/apps/renovate) is hosted by Mend.
 If you are a user of this app, and have private modules, then the following is applicable.
 
 ### Private presets with public repositories
@@ -401,7 +401,7 @@ If you need to provide credentials to the hosted Renovate App, please do this:
 
 ### Access to GitHub Actions Secrets
 
-The WhiteSource Renovate App does not run using GitHub Actions, but such secrets would be a bad fit for the app anyway for the following reasons:
+The Mend Renovate App does not run using GitHub Actions, but such secrets would be a bad fit for the app anyway for the following reasons:
 
 - The app would be granted access to _all_ the repository/org secrets, not just the ones you want
 - If Renovate wants access to such secrets, it would need to ask for them from every user, not just the ones who want to use this approach (GitHub does not support the concept of optional permissions for Apps, so people do not have the option to decline)
@@ -414,7 +414,7 @@ User/Repository config refers to the in-repository config file which defaults to
 If there is a need to supply custom rules for certain repository, it can still be done using the `config.js` file and the `repositories` array.
 
 If per-repository config must be done within the repository, it is still recommended against committing secrets directly (including e.g. `.npmrc` files with tokens) and instead encrypting them with a custom public key first.
-For instructions on this, see the above section on encrypting secrets for the WhiteSource Renovate App but instead:
+For instructions on this, see the above section on encrypting secrets for the Mend Renovate App but instead:
 
 - Save a copy of the <https://app.renovatebot.com/encrypt> HTML file locally, or host it locally
 - Generate a public/private key pair for the app using the instructions in [privateKey](https://docs.renovatebot.com/self-hosted-configuration/#privatekey)
diff --git a/docs/usage/getting-started/running.md b/docs/usage/getting-started/running.md
index ae26f91eb61ecc24359071b95720fde80c2d6004..c657014ffd7dfec0de869ef6f4c371c96da88655 100644
--- a/docs/usage/getting-started/running.md
+++ b/docs/usage/getting-started/running.md
@@ -5,7 +5,7 @@ As a Renovate end user, there are two main categories of use:
 - You self-host Renovate, e.g. by running the pre-built Docker image, or
 - Someone else is hosting Renovate, and you install/configure it for the repositories you choose
 
-If someone else is hosting Renovate for you, or you are using the WhiteSource Renovate App on GitHub, then you can skip ahead to the [installing & onboarding](./installing-onboarding.md) page.
+If someone else is hosting Renovate for you, or you are using the Mend Renovate App on GitHub, then you can skip ahead to the [installing & onboarding](./installing-onboarding.md) page.
 
 ## Self-Hosting Renovate
 
@@ -57,9 +57,9 @@ The Renovate team provide a ["Renovate Runner"](https://gitlab.com/renovate-bot/
 This supports both `gitlab.com` as well as self-hosted GitLab.
 Details for how it works can be found in the project.
 
-#### WhiteSource Renovate On-Premises
+#### Mend Renovate On-Premises
 
-WhiteSource Renovate On-Premises (WSOP) started out as a commercial product "Renovate Pro", but was renamed and made free to use when Renovate became a part of WhiteSource in 2019.
+Mend Renovate On-Premises (WSOP) started out as a commercial product "Renovate Pro", but was renamed and made free to use when Renovate became a part of Mend (formerly WhiteSource) in 2019.
 It is built similarly to the "full" Renovate image described above, but with these differences:
 
 - It is a stateful app and does not exit once it's processed all repositories
@@ -71,16 +71,16 @@ It is built similarly to the "full" Renovate image described above, but with the
 WSOP supports GitHub (both `github.com` and GitHub Enterprise Server) as well as GitLab self-hosted.
 Documentation can be found in its public GitHub repository [`whitesource/renovate-on-prem`](https://github.com/whitesource/renovate-on-prem).
 
-#### WhiteSource Remediate
+#### Mend Remediate
 
-[WhiteSource Remediate](https://www.whitesourcesoftware.com/wp-content/media/2021/04/whitesource-remediation-solution.pdf) is an extension of WSOP available for WhiteSource commercial customers, with full enterprise support.
-It is integrated with WhiteSource's vulnerability detection capabilities and additionally supports the capability of "horizontal" scalability - the ability to configure many Renovate "worker" containers which share a common job queue in order to not conflict with each other.
+[Mend Remediate](https://www.whitesourcesoftware.com/wp-content/media/2021/04/whitesource-remediation-solution.pdf) is an extension of WSOP available for Mend commercial customers, with full enterprise support.
+It is integrated with Mend's vulnerability detection capabilities and additionally supports the capability of "horizontal" scalability - the ability to configure many Renovate "worker" containers which share a common job queue in order to not conflict with each other.
 
-WhiteSource Remediate supports GitHub Enterprise Server, GitLab self-hosted, and Bitbucket Server.
+Mend Remediate supports GitHub Enterprise Server, GitLab self-hosted, and Bitbucket Server.
 
 #### Forking Renovate app
 
-"Forking Renovate" is the sister app to the WhiteSource Renovate App on GitHub.com.
+"Forking Renovate" is the sister app to the Mend Renovate App on GitHub.com.
 The difference is that Forking Renovate does not require `write` permissions to create branches within the repo, and instead submits PRs from its own fork.
 Because of how it works, it functions on public repositories only and additionally cannot support `automerge` capabilities.
 
@@ -108,7 +108,7 @@ For the npm package approach or Docker images, you will need some form of VM or
 In all the above cases you will need to make sure that some form of cron-like capability exists to schedule when Renovate runs.
 In general we recommend to run Renovate hourly if possible.
 
-WhiteSource Renovate On-Premises and WhiteSource Remediate both run as long-lived containers so do not need any additional cron-like concept as it is built-in.
+Mend Renovate On-Premises and Mend Remediate both run as long-lived containers so do not need any additional cron-like concept as it is built-in.
 
 ### Global config
 
diff --git a/docs/usage/key-concepts/automerge.md b/docs/usage/key-concepts/automerge.md
index b8b9eeefe805b225cb51cff64ccb9064ff916bf3..71b8a77982208d9637cf5492030ef515d345419f 100644
--- a/docs/usage/key-concepts/automerge.md
+++ b/docs/usage/key-concepts/automerge.md
@@ -145,7 +145,7 @@ If you have configured your project to require Pull Requests before merging, it
 
 If you have mandatory Pull Request reviews then it means Renovate can't automerge its own PR until such a review has happened.
 
-If you are running the hosted WhiteSource Renovate App on `github.com`, you can also install the helper apps [renovate-approve](https://github.com/apps/renovate-approve) and [renovate-approve-2](https://github.com/apps/renovate-approve-2) and they will mark all automerging Pull Requests by Renovate as approved.
+If you are running the hosted Mend Renovate App on `github.com`, you can also install the helper apps [renovate-approve](https://github.com/apps/renovate-approve) and [renovate-approve-2](https://github.com/apps/renovate-approve-2) and they will mark all automerging Pull Requests by Renovate as approved.
 These approval helper apps are only available for GitHub.
 
 ### Codeowners
diff --git a/docs/usage/node.md b/docs/usage/node.md
index 0acd3d0b52a246595b2c2b4d0aed0b82adefbf3a..f7588e91563a9818c3970adba49ed50370135e45 100644
--- a/docs/usage/node.md
+++ b/docs/usage/node.md
@@ -24,7 +24,7 @@ Renovate can manage the Node.js version in the following files:
 
 ## Configuring which version of npm Renovate uses
 
-When `binarySource=docker`, such as in the hosted WhiteSource Renovate App, Renovate will choose and install an `npm` version dynamically.
+When `binarySource=docker`, such as in the hosted Mend Renovate App, Renovate will choose and install an `npm` version dynamically.
 
 To control which version or constraint is installed, you should use the `engines.npm` property in your `package.json` file.
 Renovate bot will then use that version constraint for npm when it creates a pull request.
diff --git a/docs/usage/php.md b/docs/usage/php.md
index a66ee81d2a262ecc3636d66f5937fbe0f60cfac4..631ac8ebada2fbad93523e8ef99740f87f4f9fd0 100644
--- a/docs/usage/php.md
+++ b/docs/usage/php.md
@@ -42,7 +42,7 @@ If you are using a [privately hosted Composer package](https://getcomposer.org/d
 ```
 
 This host rule is best added to the bot's `config.js` config so that it is not visible to users of the repository.
-If you are using the hosted WhiteSource Renovate App then you can encrypt it with Renovate's public key instead, so that only Renovate can decrypt it.
+If you are using the hosted Mend Renovate App then you can encrypt it with Renovate's public key instead, so that only Renovate can decrypt it.
 
 Go to [https://app.renovatebot.com/encrypt](https://app.renovatebot.com/encrypt), paste in the secret string you wish to encrypt, click _Encrypt_, then copy the encrypted result.
 You may encrypt your `password` only, but you can encrypt your `username` as well.
diff --git a/docs/usage/security-and-permissions.md b/docs/usage/security-and-permissions.md
index 881afd71bcbadc4f72a009ff12fdfb1b9095162b..77c70ad5ee0b7716b8bd63e7102c378cab7db9c3 100644
--- a/docs/usage/security-and-permissions.md
+++ b/docs/usage/security-and-permissions.md
@@ -10,7 +10,7 @@ That said, we will try to fix security problems in a reasonable timeframe if pos
 ### No certifications
 
 Renovate the Open Source project does **not** have ISO 27001 or SOC2 certifications.
-WhiteSource the company, which maintains Renovate and operates the hosted Renovate App for GitHub, does have ISO 27001 and SOC2 certifications.
+Mend the company, which maintains Renovate and operates the hosted Renovate App for GitHub, does have ISO 27001 and SOC2 certifications.
 
 ### Security / Disclosure
 
diff --git a/docs/usage/troubleshooting.md b/docs/usage/troubleshooting.md
index 83b32bee848a29e53b91e72437a2f99d6aa1bba8..17a35bb0781ade350456772ccb9689e9735e8337 100644
--- a/docs/usage/troubleshooting.md
+++ b/docs/usage/troubleshooting.md
@@ -9,13 +9,13 @@ Where you can find the logs depends on how you're running Renovate.
 
 ### GitHub Hosted app
 
-Each pull request from Renovate has a link to the WhiteSource Renovate Dashboard in the PR body text.
+Each pull request from Renovate has a link to the Mend Renovate Dashboard in the PR body text.
 
 The text you're looking for is:
 
-> This PR has been generated by WhiteSource Renovate. View repository job log here.
+> This PR has been generated by Mend Renovate. View repository job log here.
 
-Click on the blue text "here" to go to the WhiteSource Renovate App Dashboard.
+Click on the blue text "here" to go to the Mend Renovate App Dashboard.
 Sign in with your GitHub or GitLab account.
 Once you're logged in, you can see the logs for the Renovate jobs on your repository.
 You should have access to any repository which you have write access to and which has Renovate installed.
diff --git a/lib/modules/manager/bundler/readme.md b/lib/modules/manager/bundler/readme.md
index 4580a2a89b8a9daca583f6f91e583f0b6a562518..03cd0129d814f85e694e190b07ff56c7c25edccf 100644
--- a/lib/modules/manager/bundler/readme.md
+++ b/lib/modules/manager/bundler/readme.md
@@ -29,4 +29,4 @@ Instead of `token`, you may also supply `username` and `password` instead.
 If you don't want to commit raw secrets to your repository, either:
 
 - If self hosting, add the `hostRules` to your bot's configuration file rather than the repository's configuration file, or
-- If using the hosted WhiteSource Renovate app, make use of the [`encrypted`](https://docs.renovatebot.com/configuration-options/#encrypted) capability
+- If using the hosted Mend Renovate app, make use of the [`encrypted`](https://docs.renovatebot.com/configuration-options/#encrypted) capability
diff --git a/lib/modules/manager/gomod/readme.md b/lib/modules/manager/gomod/readme.md
index 0610e6bdf7b5707e55636dc879a5c84a1afbaf49..4071564367a385b36115779e445361873a86181d 100644
--- a/lib/modules/manager/gomod/readme.md
+++ b/lib/modules/manager/gomod/readme.md
@@ -6,5 +6,5 @@ You might be interested in the following `postUpdateOptions`:
 1. `gomodUpdateImportPaths` - if you'd like Renovate to update your source import paths on major updates before raising the PR.
 1. `gomodNoMassage` - to skip massaging of `replace` statements.
 
-When Renovate is running using `binarySource=docker` (such as in the hosted WhiteSource Renovate app) then it will pick the latest compatible version of Go to run, i.e. the latest `1.x` release.
+When Renovate is running using `binarySource=docker` (such as in the hosted Mend Renovate app) then it will pick the latest compatible version of Go to run, i.e. the latest `1.x` release.
 Therefore even if the `go.mod` has a version like `go 1.14`, you will see Renovate treating that as a `^1.14` constraint and not `=1.14`.