Dependency analysis on package lokern

General information

CRAN link link
Package version1.1-9
Number of strong dependencies6
Number of all dependencies6
Number of parent packages5
Max heaviness from parent packages2
Total heaviness from parent packages3
Number of parent packages (including Suggests and Enhances)5
Max co-heaviness from parent packages ("sfsmisc" and "grDevices")1

Dependency heatmap

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

Adjust heatmap size:
Base packages Imports grDevices utils stats tools 0 1 2 3 Imported methods 0 2 4 Required packages 0 1 2 Heaviness from parents grDevices graphics stats utils sfsmisc In total 6 packages are required directly or indirectly (6) when installing 'lokern' (1.1-9) Imports Base packages that are required Contributed packages that are required Packages that are required for installing 'lokern' Imported functions


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on lokern
sfsmisc Imports 2 0 0 4 2
graphics Imports 2 0 0 0 1
grDevices Imports 1 0 0 0 0
stats Imports 3 0 0 0 0
utils Imports 1 0 0 0 0

Analysis was done with pkgndep.