« Trade-offs to consider when reading a large dataset into R using the RevoScaleR package | Main | Tutorial: Data Science with SQL Server R Services »

December 16, 2015


Feed You can follow this conversation by subscribing to the comment feed for this post.

Hi, that is very interesting. One thing that I have been wondering for a while, is there way to secure the source code of my R package? This came up to me some time ago when I needed to ship the package to a client along with other things.


If you don't want your client to see your source code, then you should distribute the binaries of your package, and not the source code.

But even then you should know that it is fairly simple to decompile the binaries into source code.

To protect you IP, you need to put in place license agreements with your client, and not rely on trying to obscure the source code.


The comments to this entry are closed.

Search Revolutions Blog

Got comments or suggestions for the blog editor?
Email David Smith.
Follow revodavid on Twitter Follow David on Twitter: @revodavid
Get this blog via email with Blogtrottr