• using R Under development (unstable) (2025-07-15 r88411)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.7 (3+b1)     Debian flang-new version 19.1.7 (3+b1)
• running under: Debian GNU/Linux 13 (trixie)
• using session charset: UTF-8
• checking for file ‘MoLE/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘MoLE’ version ‘1.0.1’
• checking CRAN incoming feasibility ... [1s/1s] NOTE Maintainer: ‘Sander Lestrade <samlestrade@protonmail.com>’ No Authors@R field in DESCRIPTION. Please add one, modifying   Authors@R: person(given = "Sander",                     family = "Lestrade",                     role = c("aut", "cre"),                     email = "samlestrade@protonmail.com") as necessary.
• 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 ‘MoLE’ 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 ... NOTE Problems with news in ‘NEWS.md’: No news entries found.
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [0s/0s] OK
• checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the package can be unloaded cleanly ... [0s/0s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
• checking loading without being on the library search path ... [0s/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 ... [31s/41s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) CHECKSUCCESS.Rd:44: Escaped LaTeX specials: \&
• 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 LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... [107s/144s] OK Examples with CPU (user + system) or elapsed time > 5s                  user system elapsed GROUP 4.492 0.000 5.546 SUCCESS 4.367 0.000 5.771 INTERPRET 4.276 0.000 5.109 ANALYZE 3.971 0.063 6.141 PREPARE 4.034 0.000 5.080 TURN 4.009 0.000 5.583 GENERALIZE 3.986 0.004 6.049 VERBFINAL 3.893 0.000 5.026 WORDORDER 3.812 0.000 5.641 TYPEMATCH 3.754 0.008 5.849 FIRSTINFIRSTOUT 3.717 0.005 6.269 CHECKSUCCESS 3.694 0.015 5.118 DECOMPOSE 3.705 0.000 5.939 FREQUPDATE 3.681 0.005 5.563 SELECTACTOR 3.682 0.000 5.017 PROPOSITION 3.603 0.000 5.175
• checking PDF version of manual ... [6s/8s] OK
• checking HTML version of manual ... [2s/3s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 3 NOTEs