Description
Seal fixes the open source vulnerabilities Cycode surfaces across your software supply chain. 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 alongside Cycode like any other dependency.
How Seal fits into your Cycode workflow
Cycode gives security teams a single view of risk across the software development lifecycle, including the open source dependencies in your applications; Seal is the fix for what it finds there. Add the Seal CLI as a step in your CI pipeline, and it resolves the packages covered by your Sealing Rules to their sealed versions during the build, before the rest of the pipeline runs. The sealed package ships through your pipeline like any other dependency, with no separate Cycode-specific step.
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 pipeline 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 Cycode-monitored project 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, pom.xml 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 Cycode's findings
Keep Cycode running. Seal does not replace it; Seal removes the vulnerability it reports. Once the Seal CLI has run and the sealed version is in your lockfile, the next scan Cycode runs sees the sealed package instead of the original and the finding closes. Your Cycode dashboard keeps showing real, open risk across your SDLC, while the open source issues Seal has fixed no longer raise alerts, block releases or crowd your security backlog.
Setting up Seal with Cycode
- Get a Seal API token from the Seal Platform.
- Connect Seal to your CI secrets store, or add the token directly to your pipeline configuration.
- Add a Seal CLI step to your pipeline, placed early, before your build, test or Cycode scanning steps.
- Decide how Sealing Rules should apply: automatic, remote (managed centrally in the Seal Platform), or local (a
.seal-actions.ymlfile). - Run the pipeline. The Seal CLI resolves the packages covered by your rules to their sealed versions as part of the build.
- Re-run or wait for your next Cycode scan. The finding for each sealed package closes and clears from your risk view.
Frequently asked questions
Does Seal replace Cycode?
No. Seal fixes the open source vulnerabilities Cycode surfaces; it does not replace Cycode's visibility across source code, secrets, CI/CD and dependencies. Keep Cycode running, since the Seal CLI backports the fix into the version you already use.
Do I need to change my application code to use Seal with Cycode?
No. A sealed version is a drop-in replacement with the same major version and the same API, so adopting Seal is a pipeline configuration change, not a code change.
Which stage of my pipeline should run the Seal CLI?
Run it early, before your build and Cycode scanning steps, so the scan that follows sees the sealed versions rather than the originals.
Can one Sealing Rule cover more than one project Cycode monitors?
Yes. A rule created in remote mode is managed centrally in the Seal Platform, and every pipeline that uses the affected package picks it up on its next run.
Will this work for end-of-life or legacy package versions Cycode flags?
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.
How does Cycode show that a vulnerability has been fixed by Seal?
Once the sealed version is in place, the next scan Cycode runs no longer reports the vulnerability against that component, so it drops out of your findings and risk view.


