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. Administrator Guide
  4. Composer repositories

Images and publishing

Composer repositories

Mirror Packagist for composer. The archive of each release is fetched and scanned by this box.

  1. Settings, Registries: switch on Composer repository.
  2. Add a Composer registry. For the public packages use https://repo.packagist.org.
  3. Write Composer rules: pattern monolog/monolog or symfony/*, versions 3.5.0, ^3.5 or >=3.5 <4.0.
  4. Developers add the repository and turn Packagist off. See Set up Composer.
  • The metadata lists only allowed releases. A package with none allowed is not found, and that opens a request.
  • Each release points at one exact commit. ForgeRepo™ fetches that commit's zip once, keeps and scans it, and the metadata it hands out points composer at that copy.
  • The git source of each release is taken out, so composer can not fall back to cloning it.
  • A release that can not be fetched as a fixed zip is left out: one with only a git source, one pinned to a branch, or a tarball. An archive on an internal address is never fetched.
  • Advisories come from OSV. Malware scanning, licenses, the kill switch, auto approve and Cache now all work.
  • Branches (dev versions) are not served.