Occasionally, proprietary R packages are distributed with "byte-compiled" code using the compiler package. If you see bytecode: 0x... when inspecting a function, standard printing will not show the logic.
If you're dealing with proprietary software or protected scripts and need to decompile, consider reaching out to software developers or specific forums focused on software reverse engineering. decompile progress .r file
In a professional reverse engineering workflow, "progress" is tracked by the Decompilation Yield. This is a rough formula used to estimate how much work remains. If you're dealing with proprietary software or protected
$$ \textYield = \frac\textPseudo-code Functions\textTotal Functions \times 100 $$ In a professional reverse engineering workflow
If you are using a tool like Ghidra or IDA Pro on a binary .r file: