Step-by-Step Setup Guide
This guide walks you through the initial account setup, token generation, and connecting your first project to Seal Security.
Account Creation & Token Generation
Follow these steps to access the platform and prepare your environment. If you already have a token, you can skip to the next section.
Access the Invite: Click on the Sign in > button in the Seal Security invite email you received.
Log In: Log in to the platform using your password or social login credentials.
Start Onboarding: We're starting the onboarding flow. Click Next > to begin.
Generate Token: First, you must generate a token to Seal's artifact server. This allows you to download our sealed versions.

Generate: Click on Generate token.
Copy: Copy the newly generated token using the copy icon at the right of the text box.
Important: You will need this token later. While it should eventually be saved in a secure location (like a password manager or secret store), copy it now for immediate use in the next steps.
Continue: Click Next >.
Click Next > and then click on GitHub.
Grant Access and Install Bot: You need to give the Seal Security Bot access to the relevant repositories:
Connect to your GitHub account.
Install the Seal Security Bot. In this screen, you will be asked to select the relevant GitHub organization, and then decide whether to give the Seal app access to all its repositories or to select specific ones.
After you've selected which repositories you're giving access to, you'll return to the onboarding flow.

Grant Access and Install Bot
Choose your import method: Automatic (Bulk) or Manual (One-by-one).
Path A1: Manual Import

Manual Import Paste the path to your repository. You can add up to 3 repositories at once.
Give each repository a name.
Click Import.
Path A2: Automatic (Bulk) Import

Automatic Import Review the list of dependency files detected in your repository.
Select the specific dependency files you wish to scan.
Click Import.
View Protection page: You will land on the Protection screen.
Status: Since no projects are connected yet, we are not showing any results.
Next Step: We are now going to populate this data using the CLI.

Configure the Artifact Server
To pull sealed versions, you must configure your environment to trust and prioritize Seal's repository. Choose the scenario that matches your infrastructure.
Prerequisites
In all configurations below, you will need the following values:
$SEAL_TOKEN: The Access Token you generated in the onboarding flow.$SEAL_PROJECT: Your Project ID (e.g.,my-first-project). This is used for reporting usage.
Configuration Steps:
In the root of the project run:
Sealing a package
Once you have integrated the Seal artifact server into your pipeline, follow these steps to see the results.
Last updated