Dependency analysis on package bipartite

General information

CRAN link link
Package version2.17
Number of strong dependencies54
Number of all dependencies61
Number of parent packages7
Max heaviness from parent packages19
Total heaviness from parent packages28
Number of parent packages (including Suggests and Enhances)8
Max co-heaviness from parent packages ("fields" and "sna")11

Dependency heatmap

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

Adjust heatmap size:
Base packages Other packages Depends Imports Suggests stats utils methods grDevices graphics grid splines tools parallel lattice magrittr Matrix pkgconfig glue MASS mgcv nlme tibble ellipsis fansi lifecycle pillar rlang vctrs cli crayon utf8 permute cluster statnet.common network coda spam viridis maps dotCall64 viridisLite ggplot2 gridExtra digest gtable isoband scales withr farver labeling munsell R6 RColorBrewer colorspace evaluate highr stringr yaml xfun stringi 0 5 10 Imported methods 0 20 40 Required packages 0 5 10 15 Heaviness from parents vegan sna methods permute MASS igraph fields knitr In total 54 packages are required directly or indirectly (61) when installing 'bipartite' (2.17) Depends Imports Suggests Base packages that are required Recommended packages that are required Contributed packages that are required Packages that are required for installing 'bipartite' Imported functions The whole namespace is imported


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on bipartite
sna Depends 4 0 0 25 6
vegan Depends 12 0 0 14 2
fields Imports 1 0 0 43 19
igraph Imports 3 0 0 10 1
methods Imports The whole set of functions/methods/classes from parent package is imported to the namespace of bipartite. 0 0
permute Imports 1 0 0 1 0
MASS Imports 1 0 0 5 0
knitr Suggests No object is imported into the namespace of bipartite. 12 7

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 bipartite Co-heaviness as Jaccard coeffcient
sna fields 11 0.306

Analysis was done with pkgndep.