> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/step-by-step-onboarding-guides/javascript_pnpm-no_scm-no_sca-container-artifact_server_no_jfrog-keep_names.md).

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

1. **Access the Invite:** Click on the **Sign in >** button in the Seal Security invite email you received.
2. **Log In:** Log in to the platform using your password or social login credentials.
3. **Start Onboarding:** We're starting the onboarding flow. Click **Next >** to begin.
4. **Generate Token:** First, you must generate a token to Seal's artifact server. This allows you to download our sealed versions.\
   ![Generate Token](https://2109738374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FytkIsVkwVdKiLQ2CT6Sw%2Fuploads%2Fgit-blob-a569664e986808e0888776d94944176d136e2e3f%2Fonboarding2.avif?alt=media)
   1. **Generate:** Click on **Generate token**.
   2. **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.
   3. **Continue:** Click **Next >**.
5. Click **Maybe later** to skip the GitHub integration.
6. **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. ![Empty Protection page](https://2109738374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FytkIsVkwVdKiLQ2CT6Sw%2Fuploads%2FqUsDbCDOaT1nGgD0REvo%2F4.png?alt=media\&token=7760d67a-c63c-4043-847d-cf6bf145f940)

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

We recommend using a per-project configuration by creating or editing the .npmrc file in your project's root directory.

### Configuration Steps:

1. **Prepare your credentials:**
   * **Project ID ($SEAL\_PROJECT):** e.g., `my-first-project`.
   * **Base64 Token:** You must encode your Seal Access Token (`$SEAL_TOKEN`) in base64.
     * **macOS:** `echo -n $SEAL_TOKEN | base64`
     * **Linux (Ubuntu):** `echo -n $SEAL_TOKEN | base64 -w0`
2. **Edit `.npmrc`:** Add the following content to replace the default registry with Seal Security.

   ```
   registry=https://npm.sealsecurity.io/
   //npm.sealsecurity.io/:username=$SEAL_PROJECT
   //npm.sealsecurity.io/:_password=<YOUR_BASE64_TOKEN>
   //npm.sealsecurity.io/:always-auth=true
   ```
3. **Verify:** Run the following command to check authentication:

   ```bash
   npm -d ping
   ```

   Success Output: `npm notice PONG ... npm info ok`

## Sealing a package

Once you have integrated the Seal artifact server into your pipeline, follow these steps to see the results.