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. What ForgeRepo™ does for you

Start here

What ForgeRepo™ does for you

One address for every package and image your code uses, checked before it reaches your laptop or your pipeline.

ForgeRepo™ sits between your tools and the public registries. When you run npm install, pip install or docker pull, your tool asks ForgeRepo™ at packages.example.com instead of the internet. ForgeRepo™ checks the package against your company rules, fetches it if it is allowed, and hands it back.

Your toolnpm, pip, dockerForgeRepo™packages.example.comAllowed by therules?403 and the reasonFetched from npmjs,PyPI or Docker Hub,then checkedServed to youtokennoyes
Every install goes through the same checks, from a laptop or from a pipeline.

This protects you from packages that are malicious, typosquatted, known to be vulnerable, or simply not approved yet. It also means that when a bad version is found, your security team can see who has it and stop it everywhere at once.

What you need to do

  1. Sign in to the portal at https://packages.example.com/_admin. See Signing in.
  2. Make a token. See Make a token.
  3. Point your tools at packages.example.com: npm, pip or docker.
  4. Install as usual. If something is blocked, the error says why. See When something is blocked.