Integrating with the CI
Last updated
Last updated
Our CLI is built to be easily integrated as part of an organization's CI pipeline.
If you're using GitHub actions then you can just incorporate Seal Security's own .
Just add it immediately after pulling the packages (for example with npm install
) and before any other step:
Note that this will apply every possible fix. If you prefer to select which packages to seal, then depending on your workflow either:
Use the local configuration and set fix_mode: local
.
Use the remote configuration and set fix_mode: remote
.
Add a step immediately after pulling the packages (for example with npm install
) and before any other step:
Note that this will apply every possible fix. If you prefer to select which packages to seal, then depending on your workflow either:
Use the local configuration and set --mode local
.
Use the remote configuration and set --mode remote
.
The CLI should be added as the step immediately after pulling the packages (for example with npm install
) and before anything else.
The following example shows how to directly download the latest version of the CLI from a Linux terminal.
Note that this will apply every possible fix. If you prefer to select which packages to seal, then depending on your workflow either:
Use the local configuration and set --mode local
.
Use the remote configuration and set --mode remote
.
You can also use our CLI in a docker. The CLI should be added as the step immediately after pulling the packages (for example with npm install
) and before anything else.
The following example shows how to directly download the latest version of the CLI from a Linux terminal and deploy it in a Dockerfile.
Note that this will apply every possible fix. If you prefer to select which packages to seal, then depending on your workflow either:
Use the local configuration and set --mode local
.
Use the remote configuration and set --mode remote
.