* using log directory ‘/srv/hornik/tmp/CRAN_pretest/r4subcore.Rcheck’
* using R Under development (unstable) (2026-02-11 r89406)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 21.1.8 (1+b1)
    Debian flang version 21.1.8 (1+b1)
* running under: Debian GNU/Linux forky/sid
* using session charset: UTF-8
* current time: 2026-02-12 16:01:05 UTC
* checking for file ‘r4subcore/DESCRIPTION’ ... OK
* this is package ‘r4subcore’ version ‘0.1.0’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [2s/3s] NOTE
Maintainer: ‘Pawan Rama Mali <prm@outlook.in>’

New submission

Possibly misspelled words in DESCRIPTION:
  Parsers (2:29)
  parsers (8:28)
* 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 whether package ‘r4subcore’ can be installed ... [1s/1s] OK
* 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 ... [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/0s] 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 ... [2s/2s] OK
* checking for missing documentation entries ... WARNING
Undocumented code objects:
  ‘aggregate_indicator_score’ ‘as_evidence’ ‘bind_evidence’
  ‘canon_result’ ‘canon_severity’ ‘evidence_schema’ ‘evidence_summary’
  ‘hash_id’ ‘json_safely’ ‘normalize_01’ ‘p21_to_evidence’
  ‘r4sub_run_context’ ‘register_indicator’ ‘result_to_score’
  ‘severity_to_weight’ ‘validate_evidence’ ‘validate_indicator’
All user-level objects in a package should have documentation entries.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking examples ... NONE
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ... [1s/1s] OK
  Running ‘testthat.R’ [1s/1s]
* checking PDF version of manual ... [2s/2s] OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE
Status: 1 WARNING, 1 NOTE