Artifacts
Overview
The Artifacts section displays all packages and container images stored in your JFrog Fly Registry:
- Uploaded Artifacts - Packages you or your team have published (from CI/CD or local development)
- Public Dependencies - Packages from public registries (npm, PyPI, Maven Central, etc.) that have been cached in Fly
View all supported package managers and types →
Artifact Views
View your artifacts in two places:
All Artifacts Tab
Shows every artifact in your Fly Registry:
- Artifacts uploaded from CI/CD workflows
- Artifacts uploaded locally from your development environment
- Artifacts without Git repository association
Each artifact displays its associated Git repository (if available) or shows as uploaded locally.
Git Repository View
Navigate to a specific Git repository to see artifacts associated with that repository:
- Artifacts uploaded from workflow runs and releases
- Locally uploaded artifacts when Fly can associate them with the repository’s context
Artifacts without a Git repository association appear only in the All Artifacts tab.
How Artifacts Are Displayed
List View
The main artifacts page shows a grouped view:
| Column | Description |
|---|---|
| Name | Artifact package name |
| Type | Package manager type (npm, docker, pip, etc.) |
| Latest Version | Most recent version number |
| Last Updated | When the latest version was uploaded |
| Git Repository | Repository that produced the artifact |
Grouping:
- Artifacts with the same name are grouped together
- Only the latest version is shown in the list view
- Click to expand and see all versions
Detail View
Click any artifact to see comprehensive details:
- Specific artifact version - The selected version’s details
- Complete version history - All historical versions of the artifact
- Timestamp - Upload time for each version
Artifact Actions
Download
You can download/consume artifacts in multiple ways:
- With JFrog Fly Desktop App - Use standard package manager commands automatically connected to Fly
- With your IDE - Use natural language commands via JFrog Fly MCP integration
Learn more about downloading artifacts →
Delete Versions
Admins can delete artifact versions:
- Navigate to artifact detail page
- Select version(s) to delete
- Click Delete and confirm
- Versions are permanently removed
⚠️ Warning: Deletion is irreversible. Ensure no systems depend on the version before deleting.
Artifact Lifecycle
Upload
Uploaded Artifacts are published in two ways:
CI Workflows
GitHub Actions workflows automatically upload artifacts. Learn more →
Local Development
Upload artifacts from your workstation using standard package manager commands:
- With Fly Desktop App (Recommended) - Seamless authentication and automatic configuration Learn more →
- Manual Configuration - Configure package managers directly with access tokens Learn more →
Public Dependencies are automatically cached when first requested from public registries.
Storage
All artifacts are stored in:
- JFrog Fly Registry at
<your-fly-subdomain>.jfrog.io - Secure, encrypted storage
Download
Artifacts can be downloaded by:
- Team members with appropriate access
- CI/CD workflows with OIDC authentication
- External systems with read tokens