Jenkins
Standard CI (Jenkins, GitLab CI, CircleCI): Add a shell step to download the CLI and run the seal fix command after your dependency fetch step (e.g., after npm install or go mod download).
Ecosystems and Command Usage
The seal fix command is context-aware but requires specific sub-commands depending on what you are fixing. Complex pipelines may require multiple calls to the CLI.
Supported Ecosystems
Programming Languages: Javascript, Python, Java (Maven/Gradle), Go, etc.
Linux Packages (Seal OS): RPM, APK, APT (Red Hat, Debian, Alpine, etc.).
Post-Build Artifacts: Existing JAR and Wheel files (includes extraction, replacement, and repackaging).
Multi-Context Example
If you have a pipeline that builds a Node.js app, runs on Linux, and includes a legacy JAR file, you will execute three commands in sequence:
Fix the Code: Run
seal fiximmediately afternpm install.Fix the OS: Run
seal fix osto patch C/C++ libraries and OS-level packages.Fix Artifacts: Run
seal fix fs --path ./libs/legacy-app.jarto patch the compiled file.
Quick Start Commands
Copy the command relevant to your deployment strategy below.
Remote Mode (Security Team Managed) with Renaming
Using Seal Platform rules and renaming packages to satisfy external scanners.
The "Kitchen Sink" (Java Project + OS + Post-build)
A complex pipeline running in Remote mode.
Last updated