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.
This section lists dependencies in two directions:
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:
(M) A button to import the Asset Store package.
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:
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:
|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 embedded in your project.|
|local||source||This package is located on your local disk but is external to your Unity project folder.|
|git||source||The Package Manager installed this package in your project directly from a Git repository.|
|asset store||asset||This is an Asset packageA collection of files and data from Unity projects, or elements of projects, which are compressed and stored in one file, similar to Zip files, with the
See in Glossary that you purchased or downloaded from the Asset Store.
|deprecated||asset||This package is no longer available on the Asset Store unless you have downloaded or purchased it previously. That is, it is no longer discoverable by new customers.|
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.