Dependency analysis on package mallet

General information

CRAN link link
Package version1.0
Number of strong dependencies2
Number of all dependencies2
Number of parent packages1
Max heaviness from parent packages2
Total heaviness from parent packages2
Number of parent packages (including Suggests and Enhances)1

Dependency heatmap

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

Adjust heatmap size:
Base packages Depends methods 0 0.5 1 Imported methods 0 0.5 1 Required packages 0 1 2 Heaviness from parents rJava In total 2 packages are required directly or indirectly (2) when installing 'mallet' (1.0) Depends Base packages that are required Contributed packages that are required Packages that are required for installing 'mallet' Package is listed in 'Imports' but namespace is not imported


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on mallet
rJava Depends Parent package is listed in Depends of mallet but no object from parent package is imported. 1 2

Analysis was done with pkgndep.