Dependency analysis on package inum

General information

CRAN link link
Package version1.0-4
Number of strong dependencies4
Number of all dependencies4
Number of parent packages2
Max heaviness from parent packages3
Total heaviness from parent packages3
Number of parent packages (including Suggests and Enhances)2
Max co-heaviness from parent packages ("libcoin" and "stats")1

Dependency heatmap

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

Adjust heatmap size:
Base packages Other packages Imports stats methods mvtnorm 0 1 2 3 Imported methods 0 1 2 3 Required packages 0 1 2 3 Heaviness from parents stats libcoin In total 4 packages are required directly or indirectly (4) when installing 'inum' (1.0-4) Imports Base packages that are required Contributed packages that are required Packages that are required for installing 'inum' Imported functions


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on inum
libcoin Imports 1 0 0 3 3
stats Imports 3 0 0 0 0

Analysis was done with pkgndep.