CRAN Package Check Results for Maintainer ‘Lukas Jung <jung-lukas at gmx.net>’

Last updated on 2026-04-26 02:49:44 CEST.

Package NOTE OK
moder 12
roundwork 12
scrutiny 12
unsum 8 4

Package moder

Current CRAN status: OK: 12

Package roundwork

Current CRAN status: OK: 12

Package scrutiny

Current CRAN status: OK: 12

Package unsum

Current CRAN status: NOTE: 8, OK: 4

Version: 0.2.0
Check: compiled code
Result: NOTE File ‘unsum/libs/unsum.so’: Found non-API call to R: ‘R_NamespaceRegistry’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. 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-patched-linux-x86_64, r-release-linux-x86_64

Version: 0.2.0
Check: compiled code
Result: NOTE File ‘unsum/libs/unsum.so’: Found non-API calls to R: ‘R_MissingArg’, ‘R_NamespaceRegistry’, ‘R_Srcref’, ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavor: r-release-macos-x86_64

Version: 0.2.0
Check: compiled code
Result: NOTE File 'unsum/libs/x64/unsum.dll': Found non-API call to R: 'R_NamespaceRegistry' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-release-windows-x86_64