> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/artifacts/browse-and-search.md).

# Browse and search

Navigate the global Artifacts list or a registry's Packages tab, then search by name and filter by registry, package type, or metadata.

Harness Artifacts gives you two entry points for finding artifacts:

* The global **Artifacts** list: every artifact across all registries your account can access, with search, filters, and a customizable column view.
* The **Packages** tab inside a specific registry: artifacts stored in that registry only.

Both views respect your role permissions. Artifacts you do not have **View** access to do not appear.

## Browse the global Artifacts list

1. In the navigation menu, select **Artifacts**.
2. To search by name, type in the search bar at the top of the list.
3. To filter, select **Add filter** and choose from **Registry**, **Package Types**, **Metadata**, or **User**.

The list shows available artifacts by default. To include deleted artifacts, click **Show** and select **Deleted**. Go to [Delete an artifact or version](https://developer.harness.io/artifact-registry/3.0/artifacts/delete-an-artifact.md) to understand how soft delete works.

### Default columns

The Artifacts list displays the following columns by default:

| Column            | What it shows                                                                               |
| ----------------- | ------------------------------------------------------------------------------------------- |
| Artifact Name     | The artifact identifier within its registry                                                 |
| Tags / Version    | The most recently pushed tag or version identifier                                          |
| Evaluation Status | Whether the artifact passed the Dependency Firewall policy, or N/A if no policy applies     |
| Registry          | The registry the artifact belongs to                                                        |
| Type              | The package format (Docker, Maven, npm, and so on)                                          |
| Size              | The stored size of all versions combined                                                    |
| Downloads         | Total pull and download count                                                               |
| Environments      | Active deployment count in production and non-production environments (requires Harness CD) |
| Uploaded At       | Date and time of the most recent push                                                       |

When security scanning is enabled for a registry, a **Vulnerabilities** column appears showing Critical, High, Medium, and Low finding counts for each artifact.

### Customize visible columns

The list exposes 10 of 23 available columns by default. To add or remove columns, click the column picker icon.

Columns that are hidden by default include: Tags, Package kind, Architecture, Distribution, CRAN version, Component, User, Channel, Branch, Repository, Files, Digests, and Recipe revisions. Many are format-specific: Digests is meaningful for Docker images, CRAN version for R packages, and Recipe revisions for Conan packages.

## Browse artifacts inside a registry

1. In the navigation menu, select **Registries**.
2. Click the registry you want to inspect.
3. Select the **Packages** tab.

The Packages tab shows the following columns:

| Column         | What it shows                                  |
| -------------- | ---------------------------------------------- |
| Artifact Name  | The artifact identifier                        |
| Downloads      | Total pull and download count for all versions |
| Artifacts      | The number of stored versions                  |
| Size           | Total stored size across all versions          |
| Latest Version | The most recently pushed version identifier    |
| Uploaded At    | Date and time of the most recent push          |

Click an artifact name to open its version list.

![Versions tab for an artifact, listing each version with its tag, digest, size, download count, and last updated time](https://3872764042-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6p7kagx6lOgVXV11Eevj%2Fuploads%2Fgit-blob-fe5a329094025ee848daccb375bf5585304795a7%2Fregistry-version-list.png?alt=media)

## Docker image referencing

Docker and OCI images use two kinds of identifiers:

* **Tags**: human-readable labels such as `latest` or `1.25.2`. Multiple tags can point to the same image. Deleting a tag does not remove the image.
* **Digests**: content-addressable hashes such as `sha256:620e85a7b3b4…`. A digest identifies a specific, immutable image regardless of its tags.

In the Artifacts list, an image without any tag shows **N/A** in the Tags/Version column. It is still accessible by its digest.

### Multi-architecture images

When a Docker image is built for multiple platforms with `docker buildx`, the Artifacts list shows a single entry. Expanding the row reveals individual digests for each OS and architecture combination.

You may see an entry with **unknown/unknown** as the architecture. This is an attestation manifest pushed alongside the image; it is expected behavior and does not indicate a corrupted image.

### API behavior when untagged image support is enabled

When untagged image support is enabled on your account, the API response format changes for Docker and Helm artifacts:

* The `version` field returns the digest (for example, `sha256:620e85a7b3b4…`) instead of a tag name.
* Tags move to a separate `metadata.tags` field as a list.
* Images without tags still appear in listings, identified solely by their digest.

This affects the `GetAllArtifacts`, `GetAllArtifactVersions`, and Docker and Helm detail endpoints.

{% hint style="info" %}
This behavior is by design. Digest-based identification ensures untagged images are visible in the registry. Tags remain accessible in the response but the primary identifier is the content-addressable digest.
{% endhint %}

## Filter using metadata

You can attach custom key-value pairs to artifacts and use them as filters in the Artifacts list. Select **Add filter** and choose **Metadata**, then enter the key and value you want to match.

## Troubleshooting

<details>

<summary>I deleted a tag but the image still appears in the Artifacts list</summary>

Deleting a tag removes only that label. The image stays in the registry, accessible by its digest, until you delete the version itself. To remove the image, open the artifact, go to the Versions tab, and delete the specific version by its digest.

</details>

<details>

<summary>An artifact I pushed does not appear in the Artifacts list</summary>

Check that the push completed without error. Confirm you are looking at the right scope. The global Artifacts list shows artifacts from all registries in your current account. If you pushed to a registry in a different organization or project, switch context using the scope selector at the top of the page.

</details>

## Next steps

* [Artifact version details](https://developer.harness.io/artifact-registry/3.0/artifacts/artifact-version-details.md)
* [Download an artifact](https://developer.harness.io/artifact-registry/3.0/artifacts/download-an-artifact.md)
* [Copy a version to another registry](https://developer.harness.io/artifact-registry/3.0/artifacts/copy-a-version.md)
* [Delete an artifact or version](https://developer.harness.io/artifact-registry/3.0/artifacts/delete-an-artifact.md)

{% @harness-feedback/feedback %}
