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. Vulnerabilities and safe version resolution

Security protections

Vulnerabilities and safe version resolution

Keep known vulnerable versions out of installs automatically.

ForgeRepo™ checks cached and approved versions against osv.dev on a schedule (Hours between scans of the allow list, default 24), and checks a new version when it is first downloaded. CISA KEV and FIRST EPSS add whether an advisory is exploited in the wild and how likely it is to be.

Settings for container image scanning sit on the Vulnerabilities page.

Telling developers

  • Answer npm audit: npm audit gets its answer from these findings. The dependency tree never leaves the box.
  • Warn during the install: npm prints the advisory as the package installs.
  • Record who downloaded what: every download of a vulnerable version is logged with the token and application.

Safe version resolution

Nothing on the Vulnerabilities page blocks by itself. Turn on Safe version resolution (Settings, Policy) and pick Leave out advisories from (default HIGH). Versions at or above that severity are then left out of metadata, so npm and pip pick the newest safe version within the range, and an exact download of one is refused with the advisory named.

Note

Advisories with an unknown severity are never left out. A waiver for the exact advisories lets a version back in. The Resolutions page shows what was left out and what the client picked instead.