RProtoBuf
R Interface to the 'Protocol Buffers' 'API' (Version 2 or 3)
Description
Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal 'RPC' protocols and file formats. Additional documentation is available in two included vignettes one of which corresponds to our 'JSS' paper (2016, <doi:10.18637/jss.v071.i02>. A sufficiently recent version of 'Protocol Buffers' library is required; currently version 3.3.0 from 2017 is the tested minimum.
Downloads
3.7K
Last 30 days
2091st
21K
Last 90 days
42.7K
Last year
Trend: -74% (30d vs prior 30d)
CRAN Check Status
Show all 14 flavors
| Flavor | Status |
|---|---|
| r-devel-linux-x86_64-debian-clang | NOTE |
| r-devel-linux-x86_64-debian-gcc | NOTE |
| r-devel-linux-x86_64-fedora-clang | NOTE |
| r-devel-linux-x86_64-fedora-gcc | NOTE |
| r-devel-macos-arm64 | OK |
| r-devel-windows-x86_64 | NOTE |
| r-oldrel-macos-arm64 | NOTE |
| r-oldrel-macos-x86_64 | NOTE |
| r-oldrel-windows-x86_64 | NOTE |
| r-patched-linux-x86_64 | NOTE |
| r-release-linux-x86_64 | OK |
| r-release-macos-arm64 | OK |
| r-release-macos-x86_64 | OK |
| r-release-windows-x86_64 | OK |
Check details (9 non-OK)
compiled code
File ‘RProtoBuf/libs/RProtoBuf.so’: Found non-API call to R: ‘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.
compiled code
File ‘RProtoBuf/libs/RProtoBuf.so’: Found non-API call to R: ‘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.
compiled code
File ‘RProtoBuf/libs/RProtoBuf.so’: Found non-API call to R: ‘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.
compiled code
File ‘RProtoBuf/libs/RProtoBuf.so’: Found non-API call to R: ‘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.
compiled code
File 'RProtoBuf/libs/x64/RProtoBuf.dll': Found non-API call to R: '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.
installed package size
installed size is 33.6Mb
sub-directories of 1Mb or more:
libs 32.2Mb
installed package size
installed size is 34.2Mb
sub-directories of 1Mb or more:
libs 32.7Mb
installed package size
installed size is 5.5Mb
sub-directories of 1Mb or more:
libs 4.1Mb
compiled code
File ‘RProtoBuf/libs/RProtoBuf.so’: Found non-API call to R: ‘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.
Check History
NOTE 11 OK · 3 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Mar 10, 2026
installed package size
installed size is 33.6Mb
sub-directories of 1Mb or more:
libs 32.2Mb
installed package size
installed size is 34.2Mb
sub-directories of 1Mb or more:
libs 32.7Mb
installed package size
installed size is 5.5Mb
sub-directories of 1Mb or more:
libs 4.1Mb