nilportugues/php_forbidden

Looks into the code using a user-defined list of forbidden function in a given path.

PHP Forbidden Functions

, _(*1)

Why? Because someone should look for forbidden functions that should be avoided in production., _(*2)

Typical examples are print_r, var_dump, exit and die function calls., _(*3)

Installation

Use Composer to install the package:, _(*4)

$ composer require --dev nilportugues/php_forbidden

Usage

It is really this simple:, _(*5)

$ php bin/php_forbidden check <path/to/directory>

$ php bin/php_forbidden check <path/to/file>

You can also pipe STDIN in, if you want to use this tool with Gulp for instance:, _(*6)

$ cat <path/to/file> | php bin/php_forbidden check

which means that this also works writing code directly from the shell (if you have some reason to do it):, _(*7)

$ php bin/php_forbidden check
<?php
// Insert your code
// and press CTRL+D to send EOF

Configuration file

When run the first time, if no php_forbidden_function.yml file is found, it will be generated., _(*8)

A configuration for instance, should formatted as follows:, _(*9)

forbidden:
  - file_get_contents
  - fopen
  - die
  - var_dump
  - print_r

You can specify an alternate location for the configuration file by passing in the -c parameter. Example:, _(*10)

$  php bin/php_forbidden check -c configs/php_forbidden_function.yml src/

Contribute

Contributions to the package are always welcome!, _(*11)

• Report any bugs or issues you find on the issue tracker.
• You can grab the source code at the package's Git repository.

Support

Get in touch with me using one of the following means:, _(*12)

• Emailing me at contact@nilportugues.com
• Opening an Issue

Authors

• Nil Portugués Calderó
• The Community Contributors

License

The code base is licensed under the MIT license., _(*13)