Lightwell helps protect the supply chain of open source libraries and provides many vulnerability remediations. Lightwell targets both the Common Vulnerabilities and Exposures (CVEs) that scanners are built to detect and newly discovered, or novel, vulnerabilities that scanners do not yet look for. In its first few months, Lightwell has delivered more than 800 novel vulnerability remediations. Lightwell can reduce your risk exposure and close entire attack vectors that were previously invisible to security teams.
Accessing these remediated libraries is only the first step; you also need to embed them into your software development lifecycle (SDLC) and, ideally, apply them automatically. Whether you're evaluating Lightwell for your organization or rolling out patches across an active enterprise subscription, this workflow shows how to apply remediated dependencies automatically. In this article, we use Mend Renovate, an open source dependency automation tool that runs across most continuous integration and continuous delivery (CI/CD) environments to help teams keep application dependencies up-to-date. If you use an alternative updater, many of the core integration principles and patterns discussed here will still apply.
See it in action
Watch the demonstration video of Lightwell with Mend Renovate to see automated dependency updates in action.
Why Mend Renovate?
Many tools offer dependency automation, but few are as extensible and as widely adopted as Mend Renovate. Here are the main reasons we chose Mend Renovate for Lightwell:
- First-class support for versioning and suffixes: Lightwell patches append clean release identifiers (like
.rhlw-00001or.rhlw-00002). You can define specific matching rules so your tooling treats these rebuilds as preferred upgrades rather than unexpected Semantic Versioning (SemVer) jumps. - Pluggable advisory feeds: Mend Renovate connects to ecosystem data feeds, such as Open Source Vulnerabilities (osv.dev), so your updater can evaluate vulnerability context alongside release metadata.
- Built for enterprise scale and native CI/CD runs: Whether you're running centralized GitHub Actions, GitLab CI, or self-hosted command-line runners in air-gapped environments, Mend Renovate runs as a stateless process wherever your code lives.
- Maintainer and developer friendly: Mend Renovate interacts directly with repositories through a dependency dashboard and submits pull requests (PRs), simplifying updates for end users.
Exploring the presets and repository use
Nobody wants to manually edit pom.xml files every time a security update ships. Different applications also require different patching strategies. To help on both fronts, we published standard presets in the lightwell-experience/renovate-config repository. Instead of configuring rules from scratch or relying on the default Maven resolver, you can extend the profile that matches your patching strategy:
java-remediated: The conservative baseline. It pins you to your exact library version and only bumps to the latest Lightwell rebuild (for example,3.7.1to3.7.1.rhlw-00002), applying backported security fixes without breaking API changes.java-upgrade: Follows standard Maven SemVer rules and proposes updates to.rhlwartifacts based on your update policies (for example,3.7.1to3.18.0.rhlw-00002).python-manager: Uses Python's local version identifier specification (+rhlw_). Becausepipanduvnaturally prefer these local builds, Mend Renovate keeps pinned versions up-to-date without extra version rules.
To use a preset, add an extends block to your renovate.json configuration file:
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"github>lightwell-experience/renovate-config:java-upgrade"
]
}This configuration works without extra changes if you use Renovate and build directly from the Lightwell repositories. However, we expect most enterprise developers to define a few more settings so Renovate fits within their environments and pulls from a local artifact repository, for example.
Getting started
Setting up automated remediation requires no major architectural overhaul. Whether developers trigger Mend Renovate locally or run it with centralized CI pipelines, the integration follows a straightforward lifecycle with this automation loop (Figure 1).

Prerequisites
Mend Renovate supports a wide range of platforms and fits well with both Software-as-a-Service (SaaS) and on-premise environments. Refer to the official documentation to see all supported platforms and options.
Artifact repository: You can access Lightwell repositories directly using Lightwell service accounts. However, this approach assumes broad access and using artifact repositories such as JFrog Artifactory or Sonatype Nexus might offer a better access model for larger environments. We recommend using virtual repositories that resolve dependencies in the priority order shown in Figure 2.

Source code management (SCM) platform with runners set up: Most major Git-powered platforms are good options, and chances are you're already using one. Common options include GitHub, GitLab, Gitea, and Forgejo.
Tokens: You need a GitHub token to access security metadata. If you use a different SCM platform for application repositories, you also need a user token for a bot account, as well as access tokens for Lightwell or your artifact repositories.
Application repository: Start with a Java or Python application, or try the Lightwell demonstration application! This demo is set up for the public testing repository and is easy to modify for the full Lightwell repositories when you have an active membership.
Adding Mend Renovate to your environment
If you're new to dependency automation, don't get overwhelmed by the available options. Start by using runners for your SCM platform. Not only does this approach keep things clean, but it centralizes logs so developer teams can access them in one place. Other deployment options exist when running Mend Renovate at scale across thousands of repositories in your SCM platform.
GitHub users can install the official Mend Renovate GitHub App, while teams running self-hosted Gitea instances can follow the Gitea tutorial on using Renovate Bot. Both approaches monitor your repositories and submit pull requests automatically.
Adding your application repository
Once Mend Renovate is running in your SCM platform, you can onboard an application by defining its update rules and registry settings in your repository.
Configuring renovate.json
To configure Mend Renovate for Lightwell, update your repository's renovate.json file to accomplish 3 goals:
- Inherit the Lightwell preset so Mend Renovate recognizes the
.rhlwversion precedence. - Point to your local Artifactory mirror so your tooling fetches metadata and rebuilds instead of querying public registries directly.
- Group related updates to prevent PR fatigue and keep notification noise down.
Here's an example configuration tuned for an internal Artifactory mirror (replace the placeholder values [ARTIFACT_MIRROR] and [ARTIFACT_MIRROR] or [VIRTUAL_REPO_PATH]/ for your environment):
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended",
"github>lightwell-experience/renovate-config:java-upgrade"
],
"dependencyDashboard": true,
"hostRules": [
{
"matchHost": "https://[ARTIFACT_MIRROR]",
"hostType": "maven"
}
],
"packageRules": [
{
"matchManagers": ["custom.regex"],
"matchDatasources": ["maven"],
"registryUrls": ["https://[ARTIFACT_MIRROR]/[VIRTUAL_REPO_PATH]/"]
},
{
"matchManagers": ["custom.regex"],
"matchDatasources": ["maven"],
"groupName": "all maven dependencies",
"groupSlug": "all-maven-deps"
}
]
}Let's break down what's happening in this file:
extends: Imports Mend Renovate's default configuration (config:recommended) alongsidegithub>lightwell-experience/renovate-config:java-upgrade. This configuration enables the regex and custom manager rules needed to prefer.rhlwsecurity rebuilds whenever an upgrade path exists.dependencyDashboard: Creates an issue in your repository that acts as Mend Renovate's status hub. It gives you a clean view of pending updates, rate limits, and let-me-retry buttons without cluttering your PR list.hostRules: Tells Renovate that requests heading tohttps://[ARTIFACT_MIRROR]are Maven queries. If your mirror requires basic authentication, this is also where you'd inject credentials. If you don't use local artifact repositories, add your Lightwell repository credentials here instead.packageRules(Local Artifactory redirect): The Lightwell preset defines the custom regex managers and version-matching rules so you do not have to write them manually. This rule matches those managers and pointsregistryUrlsdirectly to your internal Artifactory repository mirror.packageRules(batching PRs): Instead of Renovate peppering your team with 5 separate PRs for 5 different Maven dependencies,groupName: "all maven dependencies"bundles them into a single pull request. Your CI pipeline runs once against the whole batch, validating all dependency updates at once.
Once this file lands on your default branch, trigger the Renovate workflow manually or let the next cron run pick it up. Your initial Dependency Dashboard issue appears, followed shortly by a PR containing your Lightwell remediated artifacts.
Adding OSV vulnerability feeds
Mend Renovate also supports checking Open Source Vulnerabilities (OSV) feeds. Add the following settings to your renovate.json file to enable this feature:
"osvVulnerabilityAlerts": true,
"dependencyDashboardOSVVulnerabilitySummary": "all"Keep in mind that OSV support is currently marked as experimental in Mend Renovate. While it worked well in our testing with Lightwell, evaluate its experimental status before enabling it in production environments.
Once configured, Mend Renovate opens a pull request containing the security advisory metadata and merge controls, as shown in Figure 3.

Further automation worth exploring
Getting automated PRs is a great start, but you can optimize further. Once the baseline is working, look for operational friction in your review cycles and optimize your workflow:
- Find the manual bottlenecks (hint: it's your test suite): The biggest blocker to fast adoption isn't generating the PR, it's having the confidence to merge it. Build reliable unit and integration test coverage so PRs don't wait weeks for manual quality assurance (QA).
- Batch your updates intentionally: While micro-PRs work well for isolated services, they can flood notifications on larger repos. Use Mend Renovate's
group:allpackage rules to bundle routine patch updates into single weekly digests. - Speed up updates with automerge: For drop-in rebuilds (
java-remediated) where public APIs remain unchanged, consider enabling automerge to merge pull requests automatically once CI tests pass. This approach shrinks your exposure window down to the duration of a test suite run without touching a single button. Check out the for advanced configuration options around automerge rules and scheduling windows. - Use Mend Renovate to automate container and OS updates: Beyond application libraries, you can also use Renovate to track base container layers and coordinate image mode for Red Hat Enterprise Linux (bootc) operating system updates across server fleets.
- Go deeper with transitive dependencies: The configurations covered so far address direct dependencies. Transitive dependencies also need coverage, and you can find tools for this in the Lightwell Renovate repository and in our article on managing Java transitive dependencies with Lightwell rebuilds.
Your turn!
Pairing Mend Renovate with Lightwell reduces manual security tracking by turning tested vulnerability remediations into automated pull requests. Thanks to our friends at mend.io for partnering with us. Explore their commercial offerings for additional security and automation capabilities.
To start integrating automated remediations into your workflow, add github>lightwell-experience/renovate-config:java-remediated to your project's renovate.json on a test branch, or clone our sample application repository to see automated Lightwell pull requests in action.