Dependency analysis on package gower

General information

CRAN link link
Package version1.0.0
Number of strong dependencies0
Number of all dependencies3
Number of parent packages0
Max heaviness from parent packages0
Total heaviness from parent packages0
Number of parent packages (including Suggests and Enhances)1

Dependency heatmap

In the following dependency heatmap, rows are the parent packages of gower and columns are the dependency packages that each parent package brings in. On the right side of the heatmap, there are three barplot annotations: 1. number of imported functions/S4 methods/S4 classes from parent packages; 2. number of dependency packages from each parent package; 3. heaviness of each parent package on gower.

Adjust heatmap size:
Base packages Suggests parallel utils 0 0.5 1 Imported methods 0 1 2 Required packages 0 1 2 3 Heaviness from parents tinytest In total 0 packages are required directly or indirectly (3) when installing 'gower' (1.0.0) Suggests Base packages that are required Contributed packages that are required Packages that are required for installing 'gower'


Dependency table

"Import" information is from the NAMESPACE file of gower.

imports: number of imported functions/objects; importMethods: number of imported S4 methods; importClasses: number of imported S4 classes.

Required packages: number of strong dependency packages for each of the parent package (or in other words, number of dependency packages the parent package brings in).

Heaviness from parent on gower: number of required packages that can be reduced if moving parent package to Suggests of gower.

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on gower
tinytest Suggests No object is imported into the namespace of gower. 2 3

Analysis was done with pkgndep.