Search for Artifacts (SaaS)

📘

Note

This content describes features in Artifactory SaaS. The new Artifacts search experience is available on a gradual rollout from Artifactory SaaS version 7.151.0.

For information about searching for Artifacts in self-managed instances of Artifactory, see Apply Artifact Filters (Self-Managed).

On the Artifacts page, you can search for repositories, folders, and artifacts in JFrog Artifactory. The following information explains how to search for items in Artifactory from the Artifacts page:

• Tips for Searching Artifacts
• Search Artifacts
• Keyword Search
• Understanding Search Patterns
• Wildcards
• Keyboard Shortcuts
• Limitations of Artifact Search

Tips for Searching Artifacts

• Understand search patterns

  You can use the following methods to find items in Artifactory:

  • Single name:maven finds all repositories, folders, and artifacts whose name starts with maven.
  • Path: libs-release/org/release-1 finds items matching that path. Any path with / works, whether it starts from a repository or a subfolder.
  • Multiple names: maven org release-1 finds all repositories, folders, and artifacts whose path matches all names in any order.

  You can also select Exact matches only to return only exact results for your query. For more information, see Understanding Search Patterns.

• View recent searches

  Recent queries and last visited results appear in the search bar. You can remove queries and results from the list.

• ​​Scope your search with keywords

  Use keywords to narrow your search by a specific scope:

  • repo: scopes your search to a specific repository. For example, repo: docker-local.
  • path: scopes your search to a specific folder in a repository. For example, path: my-app/1.0.0.
  • sha: allows you to search directly for artifacts by checksum. For example, sha: sha123456. You must search for a complete checksum. Results are not returned for partial matches.

  Combine these keywords to run targeted searches. For more information, see Keyword Search.

  ✅

  Tip

  To search inside a virtual repository, you must use the repo: scope. Without specifying scope, the artifacts appear in search results in the originating local repository or local cache of the remote repository.

  You can also scope your search by selecting the relevant location in the tree. Once selected, the Find in: option appears in the search bar with the selected scope.

• Use prefix matching and wildcards

  The Artifacts search supports prefix matching by default. You can type the first few characters of a name to find matching items, without adding an explicit * wildcard character. For example, ​art​ and ​artif​ both return ​artifact​​. ​ You can add the wildcard character * in your search term for advanced pattern matching. For more information about wildcard behavior, see Wildcards.

• Use search suggestions

  Search suggestions appear when you type at least four characters, showing up to five results. Select one of the suggestions to populate the search bar and view the item in the tree. Press Enter or click Show all results to view full search results.

• Apply filters

  You can narrow down which items appear in the tree view by using filters. Filter by repository name, repository and package type, or favorites. You can also apply filters to your search results. For more information, see Apply Artifact Filters (SaaS).

  📘

  Note

  You cannot filter search results by virtual repositories. To search in a virtual repository, use the repo: keyword. For more information, see Keyword Search.

• Use keyboard shortcuts

  You can use keyboard shortcuts to navigate the search experience more easily:

  • Cmd+K or Ctrl+K: Auto-focus on search
  • Enter: Run search and show results, or select a highlighted suggestion.
  • Arrow keys: Focus and navigate through suggested searches
  • Space: Lock existing repository or path in the search bar
  • Esc: Close suggestions without selection

Search Artifacts

The Artifacts search acts across all repositories at once and provides advanced tools like keywords, filters, suggested search, and wildcards to help you find what you're looking for.

To search for Artifacts:

1. In the ​Platform​ module, navigate to ​Artifactory > Artifacts​​. The Artifacts page opens and displays the tree.

2. Optionally, apply filters to make browsing easier and refine which results appear in the tree. For more information, see ​Apply Artifact Filters (SaaS)​​.

3. Enter a search term in the text box:

   • Enter the full or partial name of an artifact, repo, or folder. You can enter one or more names. You can also search for file paths. For more information, see ​Understanding Search Patterns​​.

   • Optionally, use ​repo:​​, ​path:​​, or ​sha:​ to scope your search to a particular repository, path, or checksum. For more information, see ​Keyword Search​​.

   • You can use ​* as a wildcard for advanced pattern matching and searching across folder levels, like ​<repo_name>*<artifact_name>​​.

     📘

     Note

     Artifacts search supports prefix search only. The wildcard must be at the end of a word or a stand-in for an entire path segment, not at the beginning or in the middle of a word.

4. Optionally, select Exact matches only to limit search results to exact matches. For example, searching for exact matches fordocker-local returns only repositories, artifacts, or folders called docker-local and omits any items whose name only contains docker-local.

5. Press Enter. The search results appear in a table.

6. Optionally, do any of the following to customize your view of the search results:

   • Select ​Customize Columns​​ and choose which columns to display in the search results table.

   • Select ​Filters​​ and apply filters by item type, repository type, package type, or item creation or modification.

     📘

     Note

     You cannot filter search results by virtual repository type. To search in a virtual repository, use the repo: keyword. For more information, see Keyword Search.

7. For any item in the search results, select the actions button and click any of the following actions. Available actions may vary based on item type and user permissions:

   • ​​Show in Artifacts Tree​​: Exit the search results table and show the selected item in the tree.​
   • Add to Favorites or Remove from Favorites: Add or remove a repository from your list of Favorites. You can filter the tree by favorites to find favorite repositories easily.
   • ​​Download​​: Download the item.
   • Delete​​: Delete the item. This option is available only for folders and artifacts.

8. To return to the tree view, select the arrow next to Search Results or use the breadcrumb navigation.

   
   

Keyword Search

You can use the following keywords to scope your search:

• ​​repo:​​ scopes your search to a specific local, cached remote, virtual, or federated repository.

  The repo: scope supports one repository only. To see results from multiple repositories, run a regular search without using keywords.

• ​​path:​​ scopes your search to a specific folder in a repository.

  You can only use path: after specifying a repo: scope. path: cannot be used independently.

• ​​sha:​​ allows you to search directly for an artifact by checksum.

The following table provides examples of search terms with keywords for the scope ​npm-local/new-folder/my-app-1.0.0.tgz with a checksum <sha>​​.

Understanding Search Patterns

This section explains search patterns using the example scope ​npm-local/new-folder/my-app-1.0.0.tgz and SHA value of sha123456​​. In other words, an artifact called ​my-app-1.0.0.tgz​ with a checksum ​<sha>​​, located in folder ​new-folder​ in the ​npm-local​​ repository.

Searching by Path

The following table provides examples of path-based searches for the scope ​npm-local/new-folder/my-app-1.0.0.tgz.

Searching Multiple Names

The following table provides examples of multiple name searches for the scope ​npm-local/new-folder/my-app-1.0.0.tgz.

Searching a Single Name

The following table provides examples of single name searches for the scope ​npm-local/new-folder/my-app-1.0.0.tgz​​.

Wildcards

When using the explicit *wildcard character, the following rules apply:

• Prefix search only: The wildcard must be at the end of the search term, not in the beginning or middle. For example, art* returns artifact. This search is equivalent to art without the explicit wildcard.
• Full path segment: You can use a wildcard as a placeholder for a full path segment. For example, <repo_name>/*/<artifact_name> returns artifacts under any folder inside the specified repository. In this position, * matches across folder levels, including the / character.
• Word separators: Certain special characters are treated as word separators in search.
  • Hyphens -split a name into separate search tokens. For exmample, my-app is equivalent to searching for my and app. As a result, an item named my-application matches the query my-app because both tokens match as prefixes.
  • Dots .are not treated as word separators. A search term like artifact.jar is matched as a single token.

Keyboard Shortcuts

The Artifacts page supports keyboard shortcuts for faster and easier searching. The following table lists supported keyboard shortcuts and their functions.

Limitations of Artifact Search

The following limitations exist when searching for artifacts in the tree:

• Prefix search only​​: Prefix search is the only supported search mode for wildcards. This means that wildcards must be used at the end of a word or as a stand-in for a whole path segment, not as leading wildcards or in the middle of a phrase. For example, ​art​ returns ​artifact​ but ​act​ doesn't return ​artifact​​.
• Sorting search results​​: The sorting order of search results is fixed. Results are sorted by item type (repositories, folders, artifacts) and then by modified time. You can apply filters to narrow search results but you can't change the sort order.
• Searching archive files​​: Items within an archive file do not appear in search results.
• Repository search scope​​: Searching in virtual repositories is only supported using the repo: scope. Searching without this scope returns items in their origin repositories, either local, federated, or cached from remote.
• Checksum search​​: The ​sha:​ keyword supports only ​equals​​, not ​contains​​. This means that you must search for a complete checksum value to get results, as partial checksums do not return results.
• repo: scope: Searches can be scoped to only one repository at a time.
• Suggested search: To get search suggestions, the search term must be at least four characters long.