Product

Overview

How it works Watch it work All 35 features Screenshots How ForgeRepo™ is secured

Keep bad packages out

Malware scanning Typosquat detection Dependency confusion protection Cooling off new releases Allow lists and block lists

When something goes wrong

Kill switch Who has it Lockdown and degraded modes Vulnerability monitoring

Developers and approvals

Requests and auto approve Check, walk and review Waivers Dry run
Formats

Languages

Private npm registry PyPI proxy and private index Private NuGet feed and proxy Maven repository proxy RubyGems mirror Composer and Packagist proxy

Apple, containers and Linux

CocoaPods CDN mirror Swift package registry Docker registry mirror RPM mirror for dnf and yum APT mirror for Debian and Ubuntu

Use it as

An npm firewall Artifacts, SBOMs and lifecycle More than one node SSO, roles and allow lists
Learn

Guides

Learn secure development Secure coding Secure pipelines Unsafe vs safe Security and development

Supply chain

Supply chain attacks, 2016 to 2026 Software supply chain security
Compare Side by side, all four ForgeRepo™ vs JFrog ForgeRepo™ vs Sonatype ForgeRepo™ vs Cloudsmith
Docs

Start

Getting started Download All documentation Questions

For developers

npm setup pip setup docker login Push a Docker image CI basics

For administrators

First setup Rules and their order Six incidents, walked through Backup and upgrade
Pricing Install it
  1. Home
  2. Documentation
  3. Developer Guide
  4. Set up Composer

PHP and Composer

Set up Composer

Point Composer at the ForgeRepo™ repository in place of Packagist, and give it your token.

Add ForgeRepo™ as a repository, turn Packagist off, and save your login once for your machine:

Set up Composer to use ForgeRepo™
$ composer config repositories.company composer https://packages.example.com/composer
$ composer config repositories.packagist.org false
$ composer config --global http-basic.packages.example.com your-user-name "$REPO_TOKEN"
$ cat composer.json
{
    "name": "acme/shop",
    "require": {
        "monolog/monolog": "^3.0"
    },
    "repositories": [{
        "packagist.org": false
    },{
        "name": "company",
        "type": "composer",
        "url": "https://packages.example.com/composer"
    }]
}

Captured by running these commands against a real ForgeRepo™.

  • With Packagist off, every package comes through packages.example.com, and so does its code. Composer never goes to GitHub for it.
  • --global saves the login in your own auth.json, not in the project. Never commit a token in auth.json.
  • The user name is yours, and the password is your token.

Then install as usual:

Install packages
$ composer install
...
Updating dependencies
Lock file operations: 2 installs, 0 updates, 0 removals
  - Locking monolog/monolog (3.12.0)
  - Locking psr/log (3.0.2)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 2 installs, 0 updates, 0 removals
  - Installing psr/log (3.0.2): Extracting archive
  - Installing monolog/monolog (3.12.0): Extracting archive
Generating autoload files

Captured by running these commands against a real ForgeRepo™.

Note

A composer.lock made before you switched still points at GitHub. Run composer update once through packages.example.com, and commit the new lock file.