Last updated on 2024-11-24 15:49:58 CET.
Package | NOTE | OK |
---|---|---|
Tendril | 10 | 3 |
Current CRAN status: NOTE: 10, OK: 3
Version: 2.0.4
Check: Rd files
Result: NOTE
checkRd: (-1) Tendril.Rd:53: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:54: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:55: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:56: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:57: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:58: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:59: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:60: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:61: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:62: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:63: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:64: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:65: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:66: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) Tendril.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64
Version: 2.0.4
Check: dependencies in R code
Result: NOTE
Namespace in Imports field not imported from: ‘graphics’
All declared Imports should be used.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.