Testing the new release of the encoder in our view is a transitional version for php 84 with code generation 82 (83), since when using a bundle of multi-versions, a pattern for 82 is used. Therefore, the main, more significant release is expected with the arrival of version 15, when php will receive the final upgrade 84 (at this stage it is still RC2).

The application finally solved the versioning problem by switching to code generation for each php in 1 file (you can encrypt one file in the range from php4 to php83, in this case the file size increases proportionally) by reworking the interface and functionality of the application (as well as loaders, in this case the loader will only process its version from the file). The question also remains open why the application itself drags previous versions of the application along with itself from time to time, if the current ones are sufficiently reworked, perhaps there is some sense in this...

PHP update closes current or known vulnerabilities at the kernel level, if the project is very sensitive to data, then the update is necessary, because not everything can be solved by encrypting certain data.

We will continue to monitor events, and also update to current versions of the software.