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. Traffic, resolutions and the audit trail

Watching the system

Traffic, resolutions and the audit trail

Every registry request, every version left out, and every change made in the portal.

  • Traffic lists every registry request. Filter by package, application, environment, and blocked, served, errors or would have blocked. Click why on a row for the full reason. Export CSV or JSON.
  • Resolutions shows, while safe resolution or cooling off is on, what npm and pip were offered, what was left out and why, and which version the client pulled.
  • Utilization shows CPU, memory, disk and network for the host and for ForgeRepo™.

The Audit trail records sign ins, failed sign ins, settings, rules, users, tokens, kills, decisions and exports, with before and after values. Secrets appear as stars. Traffic is kept for Days of traffic log to keep (default 30) and the audit trail four times as long.