Overview

Load Errors   Errors encountered when loading the module. Modules with load errors
on a platform don't have their dependencies recorded on that platform,
which also screws up the combined dependency list.  

Dependencies   This is a combined list of packages required by all modules of this
package on each supported platform, plus binary dependencies if any.
Darker names, if present, represent indirect dependencies.
Purlpe names, if present, represent packages that contain modules that must be already be loaded.

Note: These are only the dependencies required for the modules to load.
Runtime dependencies, if any, are shown separately below.

Tip: You may not need all the dependencies listed here if you are not planning
to use all the modules of the package -- look at per-module dependencies below.
 

Modules   This is the list of modules for this package.
On the right column you have the required packages for each module.
Darker names, if present, represent indirect dependencies.
Purlpe names, if present, represent dependencies that must already be loaded before loading the respective module. This is the list of modules for this package.
On the right column you have the required modules for each module.
Darker names, if present, represent indirect dependencies.
Even darker names are internal dependencies.
Purlpe names are modules that must already be loaded before loading the respective module.
  P M

Binary Dependencies   Binary dependencies are the libraries that this library is
dynamically linked against.
Darker names represent indirect dependencies.

Build Order   This is the complete list of packages that need to be compiled
in the prescribed order in order to build this package.

Scripts   This is the list of scripts (tests, demos, etc.).
Unlike normal modules, scripts are not run to track dependencies.
Instead, they are just parsed for require() calls.
This means that indirect dependencies are never shown.   P M

Docs