Package Managers

This section provides a complete reference of all supported package managers, their JFrog Fly Registry paths, and configuration instructions.

Overview

JFrog Fly supports major package managers across different ecosystems. Each package manager can be used with:

• JFrog Fly Desktop App - Automatic registry configuration. Use your standard commands without specifying JFrog Fly registry paths.

• GitHub Actions - Automatic registry configuration. Use your standard commands without specifying JFrog Fly registry paths.

• Manual Configuration - For runtime environments (Kubernetes), external systems, or environments without the Desktop App or GitHub Actions. Requires explicitly configuring each package manager with your JFrog Fly registry path and access token.

All package managers benefit from public registry proxying for faster, more reliable dependency resolution.

Supported Package Managers

Containers

JFrog Fly Registry: <your-fly-subdomain>.jfrog.io/docker

Docker | Podman

JavaScript & TypeScript

JFrog Fly Registry: <your-fly-subdomain>.jfrog.io/artifactory/api/npm/npm

npm

Python

JFrog Fly Registry: <your-fly-subdomain>.jfrog.io/artifactory/api/pypi/pypi/simple

pip (PyPI) | Pipenv | Twine

Java

JFrog Fly Registry: <your-fly-subdomain>.jfrog.io/artifactory/maven

Maven | Gradle

Go

JFrog Fly Registry: <your-fly-subdomain>.jfrog.io/artifactory/api/go/go

Go

.NET

JFrog Fly Registry: <your-fly-subdomain>.jfrog.io/artifactory/api/nuget/nuget

NuGet | dotnet

Public Registry Proxying

JFrog Fly proxies public registries, providing:

• Speed - Cached public dependencies download faster
• Reliability - Available even if public registry is down (for cached dependencies)
• Unified Access - Single registry for both your private packages and public dependencies

When you request a package, JFrog Fly checks your private artifacts first, then fetches from the public registry if needed and caches it for future use.

Proxied Public Registries