Details view

In the Package Manager window, the pane on the right displays details of the selected package.

These details include the following information:

(A) The display name.

(B) The package author or Asset Store package publisher.

(C) The package version and date the package was published to the registry or the Asset Store. If available, any tagsA reference word which you can assign to one or more GameObjects to help you identify GameObjects for scripting purposes. For example, you might define and “Edible” Tag for any item the player can eat in your game. More info
See in Glossary that apply to the package also appear after the version and date information.

(D) For Unity packages, the links to open the package documentation page, the package change log (if available), and the license information. For Asset Store packages, the links to open the Asset Store package’s official page on the Asset Store, and if available, links to the publisher’s website and their support page.

(E) A brief description. By default, Unity displays only the first three lines, but you can click the More link to see the rest of it.

(F) The name of the package registry. For native Unity packages, this is always “Unity”. For scoped package registries, this matches the name property for this scoped registry in the project manifestEach Unity project has a project manifest, which acts as an entry point for the Package Manager. This file must be available in the <project>/Packages directory. The Package Manager uses it to configure many things, including a list of dependencies for that project, as well as any package repository to query for packages. More info
See in Glossary.

(G) Thumbnails of the marketing images, audio, and video available on the Asset Store for Asset Store packages. Click on the link underneath the thumbnails to open the Asset Store package’s official page on the Asset Store.

(H) Dependency information for Unity packages. By default, this section is hidden, but you can display it by enabling the Show Dependencies project setting.

This section lists dependencies in two directions:

• Is using: Whether this package depends on another package, and if so, which version. Installed packages display the status of the dependencies after the version number.
• Used by: Whether another package depends on this one, and if so, which version.

Packages without dependencies display the message “No dependencies”.

(I) Unity packages that include sample assets display the samples along with an import button. To import the sample code, click the Import button next to the sample.

(J) For Asset Store packages, the following additional information is available here:

• The disk space required and the supported versions of Unity.
• The date you purchased the Asset Store package.
• The Asset Store package’s release information, including when it was originally released and when the current version was released.
• Any labels you assigned this Asset Store package.

(K) A button to install or update a Unity package (or the Up to date message if the selected version is already installed.)

(L) Buttons to remove or disable the Unity package.

(M) A button to import the Asset Store package.

(N) Buttons to download or update the Asset Store package.

Tags

Some packages and Asset Store packages display tags next to the version number. These tags provide information about the source or state of the package:

• Source tag types indicate where the package originates from (for example, whether it comes from a local folder or is downloaded from the package registry).
• State tag types indicate the package’s stage of the development cycle. For example, whether it is custom, an experimental package, or on the release track for a specific Unity version.
• Asset StoreA growing library of free and commercial assets created by Unity and members of the community. Offers a wide variety of assets, from textures, models and animations to whole project examples, tutorials and Editor extensions. More info
  See in Glossary tags indicate that the Asset Store package originated from the Asset Store and may also indicate some special status (for example, deprecated).

Some source tags imply state tags and vice versa (for example, if a package is embedded in your project, then Unity automatically assumes it is a custom package in development, so only the custom tag appears in the details view).

The Package Manager window displays the following values:

Note: If no tag appears beside the Unity package version in the details view, that indicates that it was probably verified for a past version of Unity but is not yet verified for this release version.