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. Make a token

Access tokens

Make a token

A token lets npm, pip, docker and your pipelines prove who they are.

Your tools do not use your portal password. They use a token instead. A token is a long random string that stands for you. You can have many, one for each laptop or pipeline, and you can revoke one without touching the others.

  1. Open Tokens in the menu.
  2. Under New token, type what the token is for, like laptop or storefront-ci.
  3. Pick how many days it lasts. Shorter is safer.
  4. Click Make one.
123
  1. A name that says where the token is used
  2. How long it lasts
  3. Make the token

The token is shown once. Copy it right away and keep it in a password manager or your pipeline secrets. The page also prints the exact setup commands for packages.example.com.

123
  1. The token is shown once. Copy it now
  2. Paste these to set up npm
  3. Or log docker in with it
A new token. The real token appears where this picture says <your token>.

Careful

Treat a token like a password. Never commit it to git, paste it in chat, or put it in a Dockerfile. If one leaks, revoke it and make a new one.

Keep the token out of your files

Most tools can read the token from an environment variable. The examples in this guide use NPM_TOKEN for npm and REPO_TOKEN for pip and docker. Set it once in your shell profile:

~/.bashrc or ~/.zshrc

export NPM_TOKEN="<your token>"
export REPO_TOKEN="$NPM_TOKEN"

See also: Revoke a token, or check when it was used, Set up npm, Set up pip, Sign docker in to packages.example.com