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. Install packages with npm

npm, pnpm and Yarn

Install packages with npm

npm install and npm ci work the same way they always have.

Once npm points at packages.example.com, install the way you always do.

Install packages
$ npm install express lodash

added 69 packages, and audited 70 packages in 2s

found 0 vulnerabilities
$ npm ls --depth=0
storefront@1.0.0 /work/storefront
+-- express@4.22.3
`-- lodash@4.18.1

Captured by running these commands against a real ForgeRepo™.

Lock files and npm ci

The resolved addresses in package-lock.json point at packages.example.com. npm ci installs exactly what the lock file says, which is what a pipeline should run.

Install an existing project from its lock file
$ grep -m 2 '"resolved"' package-lock.json
      "resolved": "https://packages.example.com/accepts/-/accepts-1.3.8.tgz",
      "resolved": "https://packages.example.com/array-flatten/-/array-flatten-1.1.1.tgz",
$ npm ci

added 69 packages, and audited 70 packages in 848ms

found 0 vulnerabilities

Captured by running these commands against a real ForgeRepo™.

Note

A lock file made before you switched may still say registry.npmjs.org. That is fine: npm 7 and later swap that address for the registry you set, so npm ci still installs through packages.example.com.

npm audit

npm audit asks packages.example.com about the packages you installed. The answer comes from the advisories ForgeRepo™ knows about.

Check a project for known advisories
$ npm audit
found 0 vulnerabilities

Captured by running these commands against a real ForgeRepo™.