Interface GuessedDependency

whether this is an R-core / base package (then its version is the R version)

how many candidate versions survived every constraint

the surviving candidate versions, ascending (capped, see GuessDepVersionsQuery.maxCandidates)

Set to false when nothing narrowed the package: every version the database holds survives, so the range merely restates what is available. Its minVersion/maxVersion then say nothing about the code (an era read off the minimum would be the database's oldest release, not the script's), which a range that happens to end at the newest version does not reveal on its own.

The other packages whose version requirements this one's version choice interacts with, so the two cannot be picked independently (A 0.2.5 requiring B == 0.2.1 while A 0.3.0 requires B == 0.3.2). A partner marked (partial) only requires (or is required by) this package in some of their versions.

the raw version constraints declared for the package (>= 1.0.0, a lockfile pin, ...)

Set to false when the signature database has no record of the package at all (e.g. a Bioconductor package), distinguishing it from one the database carries but cannot constrain. Such a package has no minVersion/maxVersion and never appears in GuessDepVersionsQueryResult.assignments, so a consumer should resolve it by other means.

the other packages this one shares a version with, so its range is not independent of theirs

Set when this package was inferred purely from orphan calls: bare calls (ggplot()) that flowR could not resolve and that no loaded package defines, but whose name is exported by exactly this one package in the signature database. The symbol would be undefined were the package not loaded, so a downstream handler may attach library(package). See orphanFunctions for the calls that implicated it.

The other packages that export the orphanFunctions, each with the versions of it that would fit the calls. Attributing an orphan is a guess: the most downloaded exporter wins, and these are the ones it beat, so whoever reads the result can pick another. Ordered as the guess ranked them, best first.

per orphanFunctions entry, where the undefined call is and why it was pinned on this package

the undefined orphan function names that inferred this package (only set when orphan), e.g. ['ggplot']

the resulting range, e.g. >=1.0.0 <=1.1.4, an exact 1.1.4, or * when nothing constrains it

how many versions the database carries in total for the package (the history the candidates are drawn from)

whether the listed candidates were capped

set when the constraints contradict each other so that no version can satisfy them all

Whether the analyzed code actually uses this package (a declared-but-never-used dependency is unconstrained): either a direct call, or the project's own NAMESPACE registering an S3 method for a class this package OWNS (see PackageSignatureSource.classOwner), e.g. tseries's S3method("as.irts","zoo") marks zoo used with no direct zoo::/library(zoo) call.