Last updated on 2025-10-31 13:51:26 CET.
| Package | NOTE | OK |
|---|---|---|
| tibblify | 10 | 3 |
Current CRAN status: NOTE: 10, OK: 3
Version: 0.3.1
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-windows-x86_64
Version: 0.3.1
Check: compiled code
Result: NOTE
File ‘tibblify/libs/tibblify.so’:
Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’
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, r-release-macos-arm64, r-release-macos-x86_64
Version: 0.3.1
Check: dependencies in R code
Result: NOTE
Namespace in Imports field not imported from: ‘lifecycle’
All declared Imports should be used.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.3.1
Check: compiled code
Result: NOTE
File 'tibblify/libs/x64/tibblify.dll':
Found non-API calls to R: 'BODY', 'CLOENV', 'ENCLOS', 'EXTPTR_PROT',
'EXTPTR_TAG', 'FORMALS', 'FRAME', 'HASHTAB', 'OBJECT', 'PRENV',
'PRVALUE', 'R_PromiseExpr', 'Rf_allocSExp', 'Rf_findVarInFrame3',
'SETLENGTH', 'SET_BODY', 'SET_CLOENV', 'SET_FORMALS',
'SET_GROWABLE_BIT', 'SET_TRUELENGTH', 'STRING_PTR'
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-windows-x86_64, r-release-windows-x86_64