by naneau

A parsing PHP obfuscator

465 Stars 144 Forks Last release: Not found 38 Commits 5 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

PHP Obfuscator

Scrutinizer Code Quality

This is an "obfuscator" for PSR/OOp PHP code. Different from other obfuscators, which often use a (reversible)

based obfuscation, this tool actually parses PHP, and obfuscates variable names, methods, etc. This means is can not be reversed by tools such as UnPHP.

This library was written out of the need to obfuscate the source for a private library which for various reasons could not be shared without steps to protect the source from prying eyes. It is not technically feasible to "encrypt" PHP source code, while retaining the option to run it on a standard PHP runtime. Tools such as Zend Guard use run-time plugins, but even these offer no real security.

While this tool does not make PHP code impossible to read, it will make it significantly less legible.

It is compatible with PHP 5.3, 5.4 and 5.5, but needs PHP 5.4+ to run.


After cloning this repository (

git clone
) and installing the dependencies through Composer (
composer install
), run the following command to obfuscate a directory of PHP files:
./bin/obfuscate obfuscate /input/directory /output/directory

If you've installed this package through Composer, you'll find the

command in the relevant bin dir.


You may find that you'll need to prevent certain variables and methods from being renamed. In this case you can create a simple YAML configuration file


# Ignore variable names
    - foo
    - bar
    - baz

# Ignore certain methods names
    - foo
    - bar
    - baz

You can run the obfuscator with a configuration file through

./bin/obfuscate obfuscate /input/directory /output/directory --config=/foo/bar/config.yml

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.