How about combining all input files into one (or several) output files?
-> a road to single-file application.
There are already exist single file app. The famous one is "Composer" which composer.phar we use every time. There are several tools available that can package php applications into one phar file.
Let's experiment with preload feature which comes with php 7.4 and create a new php workflow. Let's push YAK Pro further. YAK Pro provides one or two steps on that road. Isn't "YAK Pro" stands for "Yet Another Killer Product"?
YAK Pro should be able to produce output grouped by namespace. All classes, contants and functions member are wrapped up with just a single namespace declaration. Then all namespace declaration are combined into single (or several) output files.
From the obfuscator point of view, a bloated output file means: slowdown deobfuscated process or slowdown IDE, and additional step to analize and reformat code.
How about combining all input files into one (or several) output files? -> a road to single-file application.
There are already exist single file app. The famous one is "Composer" which composer.phar we use every time. There are several tools available that can package php applications into one phar file.
Let's experiment with preload feature which comes with php 7.4 and create a new php workflow. Let's push YAK Pro further. YAK Pro provides one or two steps on that road. Isn't "YAK Pro" stands for "Yet Another Killer Product"?
YAK Pro should be able to produce output grouped by namespace. All classes, contants and functions member are wrapped up with just a single namespace declaration. Then all namespace declaration are combined into single (or several) output files.
From the obfuscator point of view, a bloated output file means: slowdown deobfuscated process or slowdown IDE, and additional step to analize and reformat code.