Dependency analysis on package getPass

General information

CRAN link link
Package version0.2-2
Number of strong dependencies2
Number of all dependencies3
Number of parent packages2
Max heaviness from parent packages1
Total heaviness from parent packages2
Number of parent packages (including Suggests and Enhances)3

Dependency heatmap

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

Adjust heatmap size:
All required packages for 'getPass' are base packages.


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on getPass
utils Imports 1 0 0 0 1
rstudioapi Imports Parent package is listed in Imports of getPass but no object from parent package is imported. 0 1
argon2 Suggests No object is imported into the namespace of getPass. 0 1

Analysis was done with pkgndep.