Version: 2020.1
List view
Finding packages

Details view

The pane on the right side of the Package Manager window displays details about the selected package.

Package details
Package details

These details include the following information:

(A) The display name.

(B) The package version (and tagA 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
, if available)

(C) The official package name from the registry. Unity packages always start with “com.unity.”.

(D) The links to open the package documentation page, the package change log (if available), and the license information.

(E) The author.

(F) The date the package was published to the registry.

(G) A brief description.

(H) Dependency information. This section lists whether this package depends on another package and which version. Installed packages indicate the status of the dependencies after the version number. Packages without dependencies display the message “No dependencies”.

(I) Packages that include sample Assets display the samples along with an import button. To import the sample code, click the Import into project button next to the sample.

(J) Button to install or update a package (or the Up to date message if the selected version is already installed.)

(K) Buttons to remove or disable the package.

(L) The manifest button, which you can click to display the package.json manifest file in the InspectorA Unity window that displays information about the currently selected GameObject, Asset or Project Settings, alowing you to inspect and edit the values. More info
See in Glossary
view. If this is a local or an embedded package, you can edit it directly in the Inspector; otherwise, it is read-only.

Tags

Some packages display tags next to the version number. These tags convey 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 directory or is downloaded from the package registry).
  • State tag types indicate at the package’s stage of the development cycle. For example, whether it is in development, preview, or verified for a specific version of Unity.

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 in development, so only the in development tag appears in the details view).

The Package Manager window displays the following values:

Tag Type Meaning
Verified state Unity’s Quality Assurance team has verified this package to work with a specific version of the Editor.
Preview state This package is at an early stage of the release cycle. It might not have complete documentation, or it might not be fully validated by either the development team or Unity’s Quality Assurance team.
In Development state This package is in a very early stage of development and is embedded in your Project.
Local source This package is located on your local disk but is external to your Unity Project folder.

Note: If no tag appears beside the package version in the details view, it is production quality, which means it is fully validated, documented, supported, and incrementally updated.

Did you find this page useful? Please give it a rating:

List view
Finding packages