# Best practice using PackageCompiler.jl (or something else!) for code obfuscation and extensibility

**URL:** <https://discourse.julialang.org/t/best-practice-using-packagecompiler-jl-or-something-else-for-code-obfuscation-and-extensibility/85806>\
**Category:** General Usage\
**Tags:** question, package-compiler\
**Created:** [August 16, 2022, 1:42am UTC](https://discourse.julialang.org/t/best-practice-using-packagecompiler-jl-or-something-else-for-code-obfuscation-and-extensibility/85806 "2022-08-16T01:42:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ffevotte](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ffevotte/32/6587_2.png) [@ffevotte](https://discourse.julialang.org/u/ffevotte)\
**Post date:** [August 16, 2022, 7:22am UTC](https://discourse.julialang.org/t/best-practice-using-packagecompiler-jl-or-something-else-for-code-obfuscation-and-extensibility/85806/2 "2022-08-16T07:22:32Z")

</div>

As for the “obfuscation” part, the following paragraph from the PackageCompiler documentation comes to mind:

[https://julialang.github.io/PackageCompiler.jl/dev/apps.html#Reverse-engineering-the-compiled-app](https://julialang.github.io/PackageCompiler.jl/dev/apps.html#Reverse-engineering-the-compiled-app)

However, IIUC part of the above might be alleviated by new 1.8 features (but I’m not sure exactly how these are meant to be used…)

> <https://github.com/JuliaLang/julia/pull/42513>
>
> This is a fairly common request to make it possible to deploy lighter-weight sys…tem images, that also hide IP to some extent (though the IR is still present; I will have another PR for that).

> <https://github.com/JuliaLang/julia/pull/42925>
>
> This is another step towards being able to ship more traditional binaries that d…on't contain compiler data, for both smaller system images and more hidden program code.

---

_[View the full topic](https://discourse.julialang.org/t/best-practice-using-packagecompiler-jl-or-something-else-for-code-obfuscation-and-extensibility/85806)._