Connecting to GitLab
Last updated
Last updated
Connecting the Seal platform to a GitLabb repository enables it to automatically sync with your projects, detect vulnerable packages, and possibly open pull requests to replace vulnerable packages with fully-compatible sealed versions.
After you click Import from GitLab on the onboarding, you will need to put a URL to your organization on GitLab, and a personal access token with the requisite permissions.
In the Project Access Tokens screen give your token a name and a distant expiration date (we recommend at least one year in the future).
The role must be Developer, Maintainer or Owner.
Give the token api access.
Create the token, and copy it to the relevant field in the Link to GitLab window shown above.
After you've configured the connection to GitLab, you'll need to connect to the relevant code projects. Each project maps to an individual dependency file, for example package-lock.json. You can choose which dependency files you want Seal to scan. Each dependency file will map to a separate project on the platform.
You can either choose from a list of automatically detected projects, or add your projects later manually by clicking on the New project button in the Projects tab.
The Project ID field is used to identify the project when communicating with the artifact server. It is meant to be used by machines, and it won't be editable later.
