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

People and access

Users and roles

Add people, pick their role, unlock them, and act as them to see what they see.

RoleAdds
viewerRead rules, packages and vulnerabilities, review a file, and their own requests.
developerTokens, requests, withdrawing their own requests, and dependency trees.
publisherPublishing npm and PyPI packages and pushing images under reserved names. Usually a CI account.
approverRules, rule imports, all requests, request and waiver decisions, kills, and purging packages.
adminSettings, users, every token, traffic, the audit trail, cache purges and backups.
  1. Under Add someone, fill in the username, name, email, role and a starting password.
  2. Click Create the account. They must change the password the first time they sign in.

Row actions

  • switch off stops an account without deleting its history. Changing a role, switching off or resetting a password ends that person's sessions.
  • unlock clears a lockout. Accounts lock after Bad passwords before a lockout (default 5) for How long a lockout lasts (default 15 minutes).
  • reset password sets a new one they must change.
  • rename keeps the role, tokens and history.
  • impersonate lets you act as a non-admin for up to 30 minutes. A red bar with Stop stays on screen, and the audit trail records every action as "admin as them".

Note

You cannot demote, switch off or delete the last admin, or remove your own admin role.

Passwords and sessions

Settings, Access tab: Shortest allowed password (default 12), lockout settings and Portal idle timeout in minutes (default 60). Passwords need three of lower case, upper case, numbers and symbols, and cannot contain the username or common words.