Description
Seal fixes the open source vulnerabilities behind your Dependabot alerts and GitHub dependency review findings. Instead of waiting on a dependency upgrade, the Seal CLI backports the upstream security fix into the exact package version your project uses and delivers it as a signed, drop-in replacement. Your manifest stays on the same major version, and the sealed package runs through your existing pipeline like any other dependency.
How Seal fits into your GitHub Advanced Security workflow
GitHub Advanced Security finds vulnerable open source dependencies two ways: Dependabot alerts flag known vulnerabilities already in your dependency graph, and dependency review flags them on a pull request before you merge. Seal is the fix for both. The Seal CLI resolves the packages covered by your Sealing Rules to their sealed versions during the build, before Dependabot's next scan or a dependency review check runs against the change.
Sealing Rules can be managed three ways: automatically, where Seal fixes every sealable vulnerability it finds; remotely, where rules are approved once in the Seal Platform and every repository that references the affected package picks them up on its next run; or locally, in a .seal-actions.yml file committed to the repository. Remote mode is what lets one approved rule reach every repository in your GitHub organization that uses a package, without a pull request against each one.
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, go.mod or requirements.txt expects. There is no framework migration and no code change, so a security fix does not turn into an engineering project.
Seal and GitHub Advanced Security's findings
Keep Dependabot alerts and dependency review enabled. Seal does not replace them; Seal removes the vulnerability they report. Once the Seal CLI has run and the sealed version is in your lockfile, GitHub's dependency graph picks up the sealed package and the Dependabot alert for it closes. On a pull request, a dependency review check run against a branch that already resolves to the sealed version no longer flags that package, since the vulnerable version is gone from the diff.
Setting up Seal with GitHub Advanced Security
- Turn on Dependabot alerts and dependency review for your repository or organization, in Settings > Code security, if they are not already enabled.
- Get a Seal API token from the Seal Platform.
- Add the Seal CLI to your workflow, early, before your build, test or dependency review steps. See the Seal integration with GitHub for how to add the Seal GitHub Action to a workflow file.
- Decide how Sealing Rules should apply: automatic, remote (managed centrally in the Seal Platform), or local (a
.seal-actions.ymlfile). - Run the workflow. The Seal CLI resolves the packages covered by your rules to their sealed versions as part of the job.
- Let GitHub refresh its dependency graph. The Dependabot alert for each sealed package closes, and dependency review stops flagging it on new pull requests.
Frequently asked questions
Does Seal replace Dependabot or dependency review?
No. Seal fixes the vulnerabilities Dependabot alerts and dependency review find; it does not scan. Keep both enabled, since the Seal CLI backports the fix into the version you already use so the finding has something to resolve against.
Do I need to change my application code to use Seal with GitHub Advanced Security?
No. A sealed version is a drop-in replacement with the same major version and the same API, so adopting Seal is a workflow configuration change, not a code change.
Does this close existing Dependabot alerts or only prevent new ones?
Both. Once the sealed version is in your lockfile, GitHub's dependency graph reflects it and the existing alert for that package closes. New pull requests that already use the sealed version will not raise the alert again.
Will dependency review still flag a pull request after Seal has sealed the package?
No. Dependency review compares the versions in the diff against known vulnerabilities. Once the diff resolves to the sealed version, there is no vulnerable version left for the check to flag.
Will this work for end-of-life or legacy package versions flagged in my repositories?
Yes. Seal backports fixes into end-of-life and legacy versions as long as the upstream source is public, so repositories pinned to old versions can still be remediated without an upgrade.


