User Guide
  • Fundamentals
    • Quick Start Guide
      • Signing Up
      • Package Discovery
        • Connecting to GitHub
        • Connecting to GitLab
        • Connecting to Azure DevOps
        • Connecting to the CI Pipeline
        • Connecting to the Artifact Server
      • Package Sealing
        • Integrating the CLI in the CI
        • Editing Dependencies
    • Deployments
      • Choosing Your Deployment
      • Automatic Remediation
      • Remote Configuration
      • Local Configuration
      • Artifact Server
    • CLI
      • Download and Installation
      • Scanning
      • Fixing All Dependencies
      • Fixing Specific Dependencies
      • Fixing OS Vulnerabilities
      • Integrating with the CI
      • Uploading Scan Results
      • Commands
      • SCA Integrations
      • JFrog Integration
      • Usage Examples
        • Sealing Application Dependencies
        • Sealing Linux Environments
    • Artifact Server
      • Generating a Token
      • Artifact Server Ordering
      • Configuring the Package Manager
        • Configuring apk
        • Configuring Composer
        • Configuring Go
        • Configuring Gradle
        • Configuring Maven
        • Configuring npm
        • Configuring pip
        • Configuring Poetry
        • Configuring yarn
        • Configuring yum
      • Clearing the Cache
      • Editing Your Dependencies
    • Web Interface
      • Rules Screen
  • APIs
    • List Vulnerable Packages
  • FAQ
  • Vulnerability Disclosure
Powered by GitBook
On this page
  • Pull directly from the artifact server
  • Pull through JFrog's Artifactory
  1. Fundamentals
  2. Artifact Server
  3. Configuring the Package Manager

Configuring Composer

How to configure the npm package manager

PreviousConfiguring apkNextConfiguring Go

Last updated 3 months ago

This page explains how to configure the Composer package manager to pull packages from the Seal artifact server based on your existing setup.

Make sure you have the access token for the server ready.

Pull directly from the artifact server

The Composer repository is configured via the following commands:

# Configure the repository
composer config repos.packagist composer https://packagist.sealsecurity.io/

# Configure the authentication method
composer config --auth http-basic.packagist.sealsecurity.io $PROJECT_ID $TOKEN

  1. In the $PROJECT_ID put the name of your project. This value will later be used in the reporting to indicate which project pulled which vulnerable package.

  2. In the $TOKEN we need to put the access token to the artifact server.

Pull through JFrog's Artifactory

  1. Go to JFrog's Artifactory configuration and create a new remote Composer repository.

    1. In the Basic configuration, choose whatever Repository Key you like.

    2. Set as the URL.

    3. In the User Name field use jfrog.

    4. In the Password / Access Token field paste the token you created earlier.

  2. Click the Test button. This will test whether the connection and authentication to the Seal artifact server is configured properly.

  3. Save the new repository, and set it as the top priority remote repository in the virtual repository you're using.

https://packagist.sealsecurity.io