CRAN Package Check Results for Package base64enc

Last updated on 2026-02-05 03:49:42 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1-6 2.42 18.15 20.57 OK
r-devel-linux-x86_64-debian-gcc 0.1-6 1.96 15.51 17.47 OK
r-devel-linux-x86_64-fedora-clang 0.1-6 5.00 28.65 33.65 OK
r-devel-linux-x86_64-fedora-gcc 0.1-6 5.00 26.91 31.91 OK
r-devel-windows-x86_64 0.1-6 10.00 40.00 50.00 OK
r-patched-linux-x86_64 0.1-6 2.54 16.21 18.75 OK
r-release-linux-x86_64 0.1-3 1.89 15.99 17.88 NOTE
r-release-macos-arm64 0.1-6 1.00 23.00 24.00 OK
r-release-macos-x86_64 0.1-6 4.00 65.00 69.00 OK
r-release-windows-x86_64 0.1-3 6.00 38.00 44.00 NOTE
r-oldrel-macos-arm64 0.1-6 1.00 30.00 31.00 OK
r-oldrel-macos-x86_64 0.1-6 4.00 58.00 62.00 OK
r-oldrel-windows-x86_64 0.1-6 10.00 45.00 55.00 OK

Check Details

Version: 0.1-3
Check: compiled code
Result: NOTE File ‘base64enc/libs/base64enc.so’: Found non-API call to R: ‘SETLENGTH’ 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-linux-x86_64

Version: 0.1-3
Check: compiled code
Result: NOTE File 'base64enc/libs/x64/base64enc.dll': Found non-API call to R: 'SETLENGTH' 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