Package Discovery
The first thing we need to do is discover what vulnerable packages are currently in use. In the onboarding screen you will have the option to connect the Seal platform to your source control.
Package discovery can be done in two main ways:
If you're using GitHub, GitLab or Azure DevOps, you can connect the Seal platform to your repositories. Seal's app will then scan your project dependencies and identify the vulnerable packages. To proceed with this setup click on the relevant Import button in the onboarding screen, and follow the appropriate source control specific instructions.
However, if you're not using one of the supported source controls, or prefer not to give Seal read access to your repositories, you may instead configure Seal as your artifact server. With this configuration, Seal will identify the vulnerable packages you're pulling from the server. To proceed with this setup click Skip.
It's highly recommended to use the Seal app if possible, as it provides the best coverage and gives a clear picture of your vulnerable dependencies at all time.
| With source control integration | Without it | |
|---|---|---|
Coverage | Any vulnerable dependency | Only packages that are pulled from the Seal server |
Update frequency | Always up-to-date | Only when the project is built |
Minimal permissions | Read for your projects | None |
Alerts marked as fixed | Automatically | Manually through the UI |
Last updated