• using R version 4.4.2 Patched (2024-12-26 r87469)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     gcc-14 (Debian 14.2.0-8) 14.2.0     GNU Fortran (Debian 14.2.0-8) 14.2.0
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘threejs/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘threejs’ version ‘0.3.3’
• package encoding: UTF-8
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking serialization versions ... OK
• checking whether package ‘threejs’ can be installed ... OK See the install log for details.
• checking package directory ... OK
• checking for future file timestamps ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [1s/1s] OK
• checking whether the package can be loaded with stated dependencies ... [1s/1s] OK
• checking whether the package can be unloaded cleanly ... [1s/1s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/1s] OK
• checking whether the namespace can be unloaded cleanly ... [1s/1s] OK
• checking loading without being on the library search path ... [1s/1s] OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [7s/9s] OK
• checking Rd files ... [0s/1s] NOTE checkRd: (-1) globejs.Rd:88: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:89: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:90: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:91: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:92: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:93: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:94: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:95-98: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:139-140: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:141: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:142: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:143: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:144-145: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:149: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:150: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:151: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:152: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:153: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:154: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:155: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:156: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:157: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:158: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:169: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:170: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:171: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:174: Lost braces; missing escapes or markup?    174 | The \code{@} and {.} option exhibit the best performance, consider using        | ^ checkRd: (-1) scatterplot3js.Rd:187: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:188-189: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:190-191: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:192: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:193-194: Lost braces in \itemize; meant \describe ?
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... [0s/0s] OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... [3s/4s] OK
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [1s/2s] OK   Running ‘threejs.R’ [1s/1s]
• checking PDF version of manual ... [6s/8s] OK
• checking HTML version of manual ... [1s/1s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 1 NOTE