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. Maven repositories

Images and publishing

Maven repositories

Mirror Maven Central or a private repository for mvn, Gradle and sbt, with the same checks as the other types.

  1. Settings, Registries: switch on Maven repository.
  2. Add a Maven registry. For Maven Central use https://repo1.maven.org/maven2. For Nexus or Artifactory use the repository address and a token written as username:password.
  3. Write Maven rules on groupId:artifactId. A * works anywhere, like org.apache.maven.plugins:*. Versions take 2.17.2, [2.17,2.18) or 2.17.*.
  4. Developers add a mirror to settings.xml. See Set up Maven.
  • mvn downloads its own plugins through the same repository, so a new box needs allow rules for them. org.apache.maven*, org.codehaus.plexus* and friends cover the usual ones. Audit mode shows the full list after one build.
  • Every file is checked against the .sha1 the repository publishes before it is kept. A file that does not match is refused.
  • The version list (maven-metadata.xml) holds only allowed versions, so a range resolves to an allowed one.
  • A milestone or release candidate like 5.11.0-M2 counts as an ordinary version, because poms pin them exactly. Snapshots are never served.
  • Every file is scanned for malware, checked against OSV, has its pom license read, and waits out cooling off. Auto approve and Cache now work for Maven rules too.
  • Deploying with mvn deploy is not taken yet.