Dependency analysis on package benchmarkmeData

General information

CRAN link link
Package version1.0.4
Number of strong dependencies22
Number of all dependencies72
Number of parent packages4
Max heaviness from parent packages5
Total heaviness from parent packages6
Number of parent packages (including Suggests and Enhances)8
Max co-heaviness from parent packages ("dplyr" and "tibble")15

Dependency heatmap

In the following dependency heatmap, rows are the parent packages of benchmarkmeData 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 benchmarkmeData.

Adjust heatmap size:
Base packages Other packages Imports Suggests methods utils grDevices stats graphics tools compiler parallel grid magrittr rlang crayon R6 glue lifecycle vctrs pillar ellipsis fansi pkgconfig cli utf8 tibble generics tidyselect purrr jsonlite digest httr curl mime openssl askpass sys withr yaml lazyeval rex htmltools htmlwidgets crosstalk jquerylib promises base64enc fastmap Rcpp later brio callr desc evaluate pkgload praise processx ps waldo rprojroot rstudioapi diffobj rematch2 benchmarkmeData doParallel dplyr foreach Matrix iterators codetools lattice 0 2 4 6 Imported methods 0 20 40 Required packages 0 5 10 15 20 Heaviness from parents graphics utils tibble dplyr covr DT testthat benchmarkme In total 22 packages are required directly or indirectly (72) when installing 'benchmarkmeData' (1.0.4) Imports Suggests Base packages that are required Recommended packages that are required Contributed packages that are required Packages that are required for installing 'benchmarkmeData' Imported functions The whole namespace is imported Package is listed in 'Imports' but namespace is not imported


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on benchmarkmeData
dplyr Imports The whole set of functions/methods/classes from parent package is imported to the namespace of benchmarkmeData. 20 5
graphics Imports 6 0 0 0 1
utils Imports 1 0 0 0 0
tibble Imports Parent package is listed in Imports of benchmarkmeData but no object from parent package is imported. 15 0
benchmarkme Suggests No object is imported into the namespace of benchmarkmeData. 41 20
testthat Suggests No object is imported into the namespace of benchmarkmeData. 36 19
covr Suggests No object is imported into the namespace of benchmarkmeData. 20 15
DT Suggests No object is imported into the namespace of benchmarkmeData. 20 15

The following table lists pairs of parent packages with co-heaviness larger than 10. The co-heaviness measures the number of additional dependencies that two parent packages simultaneously import and are only imported by the two parents.

Note the co-heaviness from parents can be always easily observed in the dependency heatmap.

Parent 1 Parent 2 Co-heaviness on benchmarkmeData Co-heaviness as Jaccard coeffcient
tibble dplyr 15 0.75

Analysis was done with pkgndep.