User Guide
  • Fundamentals
    • Quick Start Guide
      • Signing Up
      • Package Discovery
        • Connecting to GitHub
        • Connecting to GitLab
        • Connecting to Azure DevOps
        • Connecting to the CI Pipeline
        • Connecting to the Artifact Server
      • Package Sealing
        • Integrating the CLI in the CI
        • Editing Dependencies
    • Deployments
      • Choosing Your Deployment
      • Automatic Remediation
      • Remote Configuration
      • Local Configuration
      • Artifact Server
    • CLI
      • Download and Installation
      • Scanning
      • Fixing All Dependencies
      • Fixing Specific Dependencies
      • Fixing OS Vulnerabilities
      • Integrating with the CI
      • Uploading Scan Results
      • Commands
      • SCA Integrations
      • JFrog Integration
      • Usage Examples
        • Sealing Application Dependencies
        • Sealing Linux Environments
    • Artifact Server
      • Generating a Token
      • Artifact Server Ordering
      • Configuring the Package Manager
        • Configuring apk
        • Configuring Composer
        • Configuring Go
        • Configuring Gradle
        • Configuring Maven
        • Configuring npm
        • Configuring pip
        • Configuring Poetry
        • Configuring yarn
        • Configuring yum
      • Clearing the Cache
      • Editing Your Dependencies
    • Web Interface
      • Rules Screen
  • APIs
    • List Vulnerable Packages
  • FAQ
  • Vulnerability Disclosure
Powered by GitBook
On this page
  1. Fundamentals
  2. Quick Start Guide
  3. Package Sealing

Integrating the CLI in the CI

PreviousPackage SealingNextEditing Dependencies

Last updated 9 months ago

The Seal CLI was designed to be easily integrated as part of an organization's CI pipeline.

The Seal CLI will replace vulnerable packages according to the way it's configured. This includes a possibility for , whereby any vulnerable package is automatically replaced with its sealed version, as well as that can give developers and security teams varying degrees of control over the process.

By using the CLI Seal can provide you with the clearest picture of what vulnerable package you're using where, as well as track the deployment of sealed packages throughout the organization. Moreover, using the CLI bypasses a lot of quirky behaviors of individual package managers, thereby simplifying the sealing process even for manual users.

There are two main setups that are presently supported:

  1. GitHub actions - For instructions about how to use Seal's GitHub Action see .

  2. Other CI platforms - For instructions about how to integrate Seal's CLI into other CI platforms see .

To quickly run an example on your machine without configuring your CI see the usage examples.

complete automation
other configurations
here
here