Description
Seal fixes the open source vulnerabilities Sonatype finds, and serves the fix through the registry your builds already pull from. Instead of waiting on a dependency upgrade, Seal backports the upstream security fix into the exact package version your project uses and delivers it as a signed, drop-in replacement. Sonatype Lifecycle recognizes a sealed package as remediated out of the box, and Sonatype Nexus can pull sealed packages directly, so the fix reaches your builds with no manifest edit and no pipeline change.
How Seal fits into your Sonatype workflow
Add the Seal Artifact Server as a remote repository in Nexus Repository Manager for each ecosystem you seal, such as npm, Maven, PyPI and Go, and include it in the group repository your builds already resolve against. Developers and build tools keep pulling from Nexus exactly as before; Nexus resolves the sealed version the same way it resolves any other package.
Sealing Rules decide which vulnerabilities get fixed and can be managed two ways in a registry setup: automatically, where Seal fixes every sealable vulnerability it finds, or remotely, where rules are created and approved once in the Seal Platform and every build that references the affected package picks up the sealed version on its next pull. One approved rule reaches every project that resolves packages through that group repository, with no pull request and no change to any build file.
Because a sealed version keeps the original version number and adds a suffix (for example lodash 4.17.20-sp1), it is still the version your package.json, pom.xml or other manifest expects. There is no framework migration and no code change, so a security fix does not turn into an engineering project.
Seal and Sonatype Lifecycle
Keep Sonatype Lifecycle running. Seal does not replace it; Seal removes the vulnerability it reports. Sonatype natively recognizes a sealed package as remediated, identifying it as fixed instead of matching it back to the vulnerable upstream version. Because the support is built into Sonatype, there is nothing to install or configure. Once a sealed package is in place, the vulnerability it resolves is cleared from Sonatype's findings, so a scan run by your own security team, by external auditors, or by your customers reflects the patched state of your software without manual overrides or waivers.
Setting up Seal with Sonatype
- Get a Seal API token from the Seal Platform.
- In Nexus Repository Manager, create a proxy repository for each ecosystem you want to seal, pointed at the Seal Artifact Server.
- Add each new proxy repository to the group repository your builds and package managers already resolve against.
- Decide how Sealing Rules should apply: automatic, or remote (managed centrally in the Seal Platform and picked up by every build that uses the affected package).
- Run a build. Nexus resolves the sealed version through the new remote the same way it resolves any other package.
- Re-run or wait for your next Sonatype Lifecycle scan. The finding for each sealed package clears automatically, with no configuration needed.
Frequently asked questions
Does Seal replace Sonatype Lifecycle?
No. Seal fixes the vulnerabilities Sonatype finds; it does not scan. Keep Sonatype Lifecycle running, since Seal backports the fix into the version you already use.
Do I need to configure Sonatype to recognize sealed packages?
No. Sonatype recognizes sealed packages as remediated out of the box, so there is nothing to install or set up on the Sonatype side.
Do I need to change my build files to use Seal with Nexus?
No. A sealed version is a drop-in replacement with the same major version and the same API, so adopting Seal is a repository configuration change, not a code or build-file change.
Can one Sealing Rule cover every project that pulls from Nexus?
Yes. A rule created in remote mode is managed centrally in the Seal Platform, and every build that resolves the affected package through your group repository picks it up on its next pull.
Will this work for end-of-life or legacy package versions in my Nexus instance?
Yes. Seal backports fixes into end-of-life and legacy versions as long as the upstream source is public, so pinned old versions can still be remediated without an upgrade.
Can I use Seal with Sonatype without routing packages through Nexus?
Yes. The Seal CLI can run as a step in your CI pipeline instead, resolving covered packages to sealed versions during the build, independent of which registry you use.


