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. Features
  3. Typosquat detection

Keep bad packages out

Typosquatting detection for npm and PyPI

A typosquat is a package whose name imitates one everyone uses: lodahs for lodash, reqeusts for requests, python-numpy for numpy. Somebody publishes it and waits for a typo.

Every name asked for is compared against a built in list of well known npm and PyPI names, the names you add under Also protect these names, your exact allow rules, and the packages this registry serves most. It catches:

  • a letter or two out, and two letters swapped
  • separators moved or dropped, like lo-dash or pythondateutil
  • look-alike characters, like l0dash or djang0
  • extra words bolted on, like lodash-js, node-express or python-numpy
  • a scoped name flattened, like babel-preset-env for @babel/preset-env

A name that is itself well known, pinned by an exact allow rule, on a Never flag these list, or marked "not a typosquat" by an approver is never flagged. Being popular on your box protects a name from imitation, and never makes a lookalike legitimate.

In warn mode, the default, the package is still served, npm prints a TYPOSQUAT: line during the install, and the name shows under Lookalike packages. In block mode it is refused with a 403 naming what it looks like, and the refusal opens a request carrying that reason. In whitelist mode a typo usually never gets that far, since the unknown name is not on the list anyway.

packages.example.com/_admin/
Typosquat checks live under Settings, Policy, next to cooling off and safe version resolution.

In short

  • Edit distance, swaps, separators, homoglyphs, added words and flattened scopes
  • Built in npm and PyPI name lists, plus your own protected names
  • Warn during install, or refuse with a 403 that says what it imitates
  • Approvers can clear a false positive once, for good
  • Check a package warns about a lookalike before anybody installs

In the documentation

Goes well with

  • Dependency confusion protection Reserve your npm scopes, PyPI prefixes, image namespaces and NuGet ids. A public package with your internal name is never fetched.
  • Malware scanning ClamAV, a hash blocklist, your own scanner and the OpenSSF known malicious feed, on every cached file. Optionally before the first download.
  • Cooling off new releases Brand new versions wait a few days before your builds see them, which is when hijacks get caught.

One container, about two minutes

A Linux box with Docker, or one without it, and a reverse proxy for TLS. The installer does the rest and it is safe to run twice. Free, MIT licensed, nothing to sign up for.

Getting started Read the docs