Dependency analysis on package leaps

General information

CRAN link link
Package version3.1
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 leaps 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 leaps.

Adjust heatmap size:
Base packages Other packages Suggests methods DBI 0 0.5 1 Imported methods 0 1 2 Required packages 0 1 2 3 Heaviness from parents biglm In total 0 packages are required directly or indirectly (3) when installing 'leaps' (3.1) Suggests Base packages that are required Contributed packages that are required Packages that are required for installing 'leaps'


Dependency table

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

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 leaps: number of required packages that can be reduced if moving parent package to Suggests of leaps.

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

Analysis was done with pkgndep.