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. CLI

Fixing All Dependencies

PreviousScanningNextFixing Specific Dependencies

Last updated 6 months ago

The CLI enables you to to easily fix vulnerable open-source dependencies using the sealed versions created by Seal Security.

To fix the vulnerabilities in your project, the CLI replaces in-place vulnerable package with their sealed versions. To download the sealed versions you will need an to the Seal artifact.

  1. Go to the root directory of the project and install its dependencies (e.g npm install).

  2. Set the access token and project name. There are two ways to do this:

    • Set the access token in the SEAL_TOKEN environment variable, and the project name in SEAL_PROJECT.

    export SEAL_TOKEN=<token> # the access token for the server
export SEAL_PROJECT=<project-id> # the ID of the current project

    • Set the access token and project name in the .seal-config.yml configuration file in the local project directory as in the following example:

    token: <token> # the access token for the server
project: <project-id> # the ID of the current project

The project ID may include only ASCII letters, digits, underscore, hyphen or period, and mustn't be over 255 characters long.

You should use the ID of the project as shown in the Projects tab. If you use a different ID, the platform will record the pulled libraries under a different project.

  1. Run seal fix --mode all. The vulnerable packages that have a patched version will be replaced in place with the sealed version.

Note that if your CI pipeline is using JFrog's Artifactory and cannot access other servers, you need to follow the instructions instead.

access token
here