1
0
mirror of synced 2026-01-01 00:04:41 -05:00
Files
docs/content/packages/learn-github-packages/viewing-packages.md
2022-08-28 21:59:38 +00:00

70 lines
3.3 KiB
Markdown

---
title: Viewing packages
intro: 'You can see details about packages published to a repository, and narrow results by organization or user.'
product: '{% data reusables.gated-features.packages %}'
redirect_from:
- /articles/viewing-a-repositorys-packages
- /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
- /github/managing-packages-with-github-packages/viewing-packages
- /packages/publishing-and-managing-packages/viewing-packages
- /packages/manage-packages/viewing-packages
permissions: You must have at least read permissions to view a package.
versions:
fpt: '*'
ghes: '*'
ghae: '*'
ghec: '*'
---
{% data reusables.package_registry.packages-ghes-release-stage %}
{% data reusables.package_registry.packages-ghae-release-stage %}
## About package views
Your ability to view a package depends on several factors. By default, you can view all packages you have published.
Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below **only** use this type of permissions:{% ifversion not fpt or ghec %}
- Docker registry (`docker.pkg.github.com`){% endif %}
{% ifversion packages-npm-v2 %}{% else %}- npm registry{% endif %}
- RubyGems registry
- Apache Maven registry
- NuGet registry
{% ifversion fpt or ghec %}
The {% data variables.product.prodname_ghcr_and_npm_registry %} offer you the option of granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account. You can choose to use granular permissions or connect the package to a repository and inherit it's permissions. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
{% endif %}
For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages){% ifversion fpt or ghec %}" and "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility){% endif %}."
{% data reusables.package_registry.package-page-info %}
## Viewing a repository's packages
You can find and view a package located in a particular repository.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.package_registry.packages-from-code-tab %}
{% data reusables.package_registry.navigate-to-packages %}
## Viewing an organization's packages
You can find and view a package located in the repositories of an organization you belong to.
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} **Packages**.
{% data reusables.package_registry.navigate-to-packages %}
## Viewing your packages
You can find and view any package you've published across all organizations and repositories.
{% data reusables.profile.access_profile %}
2. On the top of the profile page, in the main navigation, click **Packages**.
![Project tab](/assets/images/help/package-registry/user-packages-tab.png)
{% data reusables.package_registry.navigate-to-packages %}
## Further reading
- "[Searching for packages](/search-github/searching-on-github/searching-for-packages)"