Dependency analysis for package UpSetR

General information

CRAN link link
Package version1.4.0
Number of strong dependencies41
Number of all dependencies49
Number of parent packages8
Max heaviness from parent packages20
Total heaviness from parent packages23
Number of parent packages (including Suggests and Enhances)9
Max co-heaviness from parent packages ("ggplot2" and "scales")11

Dependency heatmap

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

Adjust heatmap size:
Base packages Other packages Imports Suggests utils methods grDevices stats graphics grid splines tools glue gtable rlang farver labeling lifecycle munsell R6 RColorBrewer viridisLite magrittr colorspace digest isoband MASS mgcv scales tibble withr nlme Matrix ellipsis fansi pillar pkgconfig vctrs lattice cli crayon utf8 Rcpp evaluate highr stringr yaml xfun stringi 0 0.5 1 Imported methods 0 10 20 30 Required packages 0 5 10 15 20 Heaviness from parents utils stats methods grDevices plyr gridExtra scales ggplot2 knitr In total 41 packages are required directly or indirectly (49) when installing 'UpSetR' (1.4.0) Imports Suggests Base packages that are required Other packages that are required Packages that are required for installing 'UpSetR' Imported functions The whole namespace is imported


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on UpSetR
ggplot2 Imports The whole set of functions/methods/classes from parent package is imported to the namespace of UpSetR. 37 20
plyr Imports 1 0 0 3 2
gridExtra Imports The whole set of functions/methods/classes from parent package is imported to the namespace of UpSetR. 5 1
utils Imports The whole set of functions/methods/classes from parent package is imported to the namespace of UpSetR. 0 0
stats Imports The whole set of functions/methods/classes from parent package is imported to the namespace of UpSetR. 0 0
methods Imports The whole set of functions/methods/classes from parent package is imported to the namespace of UpSetR. 0 0
grDevices Imports The whole set of functions/methods/classes from parent package is imported to the namespace of UpSetR. 0 0
scales Imports The whole set of functions/methods/classes from parent package is imported to the namespace of UpSetR. 15 0
knitr Suggests No object is imported into the namespace of UpSetR. 12 8

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 UpSetR Co-heaviness as Jaccard coeffcient
scales ggplot2 11 0.355

Analysis was done with pkgndep.