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, the information button and 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. When you click the information button, Unity displays information about the package (for example, if the package version you requested does not match the version installed).
(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) DependencyIn the context of the Package Manager, a dependency is a specific package version (expressed in the form
package_name@package_version) that a project or another package requires in order to work. Projects and packages use the dependencies attribute in their manifests to define the set of packages they require. For projects, these are considered direct dependencies; for packages, these are indirect, or transitive, dependencies. More info
See in Glossary 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:
Packages without dependencies display the message “No dependencies”.
(I) For Asset Store packages, the following additional information is available here:
(J) 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.
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 a custom package in development, so only the custom tag appears in the details view).
The Package Manager window displays the following values:
|Released||state||Unity officially released this package and fully supports it. The Quality Assurance team has tested this version of the package and guarantees that it works with a specific version of the Editor and all other packages released for that Editor version.|
|Release Candidate||state||This version of the package is on track to be fully “released” within the next TECH stage of the current release cycle.|
|Pre-Release||state||This version of the package is at an earlier stage of development, but Unity guarantees to release it by the end of the LTS 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.|
|Experimental||state||These packages are either new packages or contain experimental modifications. Unity does not support Experimental packages because they are in the early stages of development.|
|This package is embedded in your project. Most custom package developers start by embedding a new package in their project, which is why the “Custom” label appears.|
|local||source||The Package Manager installed this package from a folder or tarball file on your local disk 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 Store package 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: This label applies only to Asset Store packages. Unity packages that have been deprecated never appear in the Unity Editor.