R is a package-based, multi-paradigm programming language mostly used for scientific software that provides an easy way to install third-party code, datasets, tests, documentation and examples through CRAN (Comprehensive R Archive Network). Prior works determined developers tend to code workarounds to bypass CRAN’s automated checks (performed when submitting a package) instead of fixing the code. This is problematic, since it reduces the quality of all available packages, and may become a threat to those analysis written in R that rely on mis-checked code. In this preliminary study, we card-sorted source code comments to understand which types of Technical Debt are most affected by this and then analysed StackOverflow (SO) conversations discussing CRAN. We determined that about a quarter of the SO posts aim to bypass a check with a workaround; the most affected are code-related problems, package dependencies, installation and feasibility. We analyse these checks and outline future steps to improve similar automated analyses.