Issues in DisallowSpaceIndentSniff.php (develop) - Issues in develop - timw4mail/HummingBirdAnimeClient - Measure and Improve Code Quality continuously with Scrutinizer

Issues (287)

Security Analysis not enabled

Cross-Site Scripting

Cross-Site Scripting enables an attacker to inject code into the response of a web-request that is viewed by other users. It can for example be used to bypass access controls, or even to take over other users' accounts.

File Exposure

File Exposure allows an attacker to gain access to local files that he should not be able to access. These files can for example include database credentials, or other configuration files.

File Manipulation

File Manipulation enables an attacker to write custom data to files. This potentially leads to injection of arbitrary code on the server.

Object Injection

Object Injection enables an attacker to inject an object into PHP code, and can lead to arbitrary code execution, file exposure, or file manipulation attacks.

Code Injection

Code Injection enables an attacker to execute arbitrary code on the server.

Response Splitting

Response Splitting can be used to send arbitrary responses.

File Inclusion

File Inclusion enables an attacker to inject custom files into PHP's file loading mechanism, either explicitly passed to include, or for example via PHP's auto-loading mechanism.

Command Injection

Command Injection enables an attacker to inject a shell command that is execute with the privileges of the web-server. This can be used to expose sensitive data, or gain access of your server.

SQL Injection

SQL Injection enables an attacker to execute arbitrary SQL code on your database server gaining access to user data, or manipulating user data.

XPath Injection

XPath Injection enables an attacker to modify the parts of XML document that are read. If that XML document is for example used for authentication, this can lead to further vulnerabilities similar to SQL Injection.

LDAP Injection

LDAP Injection enables an attacker to inject LDAP statements potentially granting permission to run unauthorized queries, or modify content inside the LDAP tree.

Header Injection

Other Vulnerability

This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.

Regex Injection

Regex Injection enables an attacker to execute arbitrary code in your PHP process.

XML Injection

XML Injection enables an attacker to read files on your local filesystem including configuration files, or can be abused to freeze your web-server process.

Variable Injection

Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.

Unfortunately, the security analysis is currently not available for your project. If you are a non-commercial open-source project, please contact support to gain access.

Sniffs/WhiteSpace/DisallowSpaceIndentSniff.php (2 issues)

Labels

Severity

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

<?php
/**
 * CodeIgniter_Sniffs_WhiteSpace_DisallowSpaceIndentSniff.
 *
 * PHP version 5
 *
 * @category  PHP
 * @package   PHP_CodeSniffer
 * @author    Thomas Ernest <[email protected]>
 * @copyright 2011 Thomas ERNEST
 * @license   http://thomas.ernest.fr/developement/php_cs/licence GNU General Public License
 * @link      http://pear.php.net/package/PHP_CodeSniffer
 */

/**
 * CodeIgniter_Sniffs_WhiteSpace_DisallowSpaceIndentSniff.
 *
 * Ensures the use of tabs for indentation.
 *
 * @category  PHP
 * @package   PHP_CodeSniffer
 * @author    Thomas Ernest <[email protected]>
 * @copyright 2011 Thomas ERNEST
 * @license   http://thomas.ernest.fr/developement/php_cs/licence GNU General Public License
 * @link      http://pear.php.net/package/PHP_CodeSniffer
 */

namespace CodeIgniter\Sniffs\WhiteSpace;

use PHP_CodeSniffer\Sniffs\Sniff;
use PHP_CodeSniffer\Files\File;

class DisallowSpaceIndentSniff implements Sniff
{

    /**
     * A list of tokenizers this sniff supports.
     *
     * @var array
     */
    public $supportedTokenizers = array(
                                   'PHP',
                                   'JS',
                                   'CSS',
                                  );


    /**
     * Returns an array of tokens this test wants to listen for.
     *
     * @return array
     */
    public function register()
    {
        return array(T_WHITESPACE);
    }//end register()


    /**
     * Processes this test, when one of its tokens is encountered.
     *
     * @param File $phpcsFile All the tokens found in the document.
     * @param int                  $stackPtr  The position of the current token
     *                                        in the stack passed in $tokens.
     *
     * @return void
     */
    public function process(File $phpcsFile, $stackPtr)
    {
        $tokens = $phpcsFile->getTokens();

        // Make sure this is whitespace used for indentation.
        $line = $tokens[$stackPtr]['line'];
        if ($stackPtr > 0 && $tokens[($stackPtr - 1)]['line'] === $line) {
            return;
        }

        if (strpos($tokens[$stackPtr]['content'], " ") !== false) {
            $error = 'Tabs must be used to indent lines; spaces are not allowed for code indentation';
            $phpcsFile->addError($error, $stackPtr, 'SpacesUsedForIndentation');
        }
    }//end process()


}//end class

?>



1			<?php
2			/**
3			* CodeIgniter_Sniffs_WhiteSpace_DisallowSpaceIndentSniff.
4			*
5			* PHP version 5
6			*
7			* @category PHP
8			* @package PHP_CodeSniffer
9			* @author Thomas Ernest <[email protected]>
10			* @copyright 2011 Thomas ERNEST
11			* @license http://thomas.ernest.fr/developement/php_cs/licence GNU General Public License
12			* @link http://pear.php.net/package/PHP_CodeSniffer
13			*/
14
15			/**
16			* CodeIgniter_Sniffs_WhiteSpace_DisallowSpaceIndentSniff.
17			*
18			* Ensures the use of tabs for indentation.
19			*
20			* @category PHP
21			* @package PHP_CodeSniffer
22			* @author Thomas Ernest <[email protected]>
23			* @copyright 2011 Thomas ERNEST
24			* @license http://thomas.ernest.fr/developement/php_cs/licence GNU General Public License
25			* @link http://pear.php.net/package/PHP_CodeSniffer
26			*/
27
28			namespace CodeIgniter\Sniffs\WhiteSpace;
29
30			use PHP_CodeSniffer\Sniffs\Sniff;
31			use PHP_CodeSniffer\Files\File;
32
33			class DisallowSpaceIndentSniff implements Sniff
34			{
35
36			/**
37			* A list of tokenizers this sniff supports.
38			*
39			* @var array
40			*/
41			public $supportedTokenizers = array(
42			'PHP',
43			'JS',
44			'CSS',
45			);
46
47
48			/**
49			* Returns an array of tokens this test wants to listen for.
50			*
51			* @return array
52			*/
53			public function register()
54			{
55			return array(T_WHITESPACE);
56			}//end register()
57
58
59			/**
60			* Processes this test, when one of its tokens is encountered.
61			*
62			* @param File $phpcsFile All the tokens found in the document.
63			* @param int $stackPtr The position of the current token
64			* in the stack passed in $tokens.
65			*
66			* @return void
67			*/
68			public function process(File $phpcsFile, $stackPtr)
69			{
70			$tokens = $phpcsFile->getTokens();
71
72			// Make sure this is whitespace used for indentation.
73			$line = $tokens[$stackPtr]['line'];
74			if ($stackPtr > 0 && $tokens[($stackPtr - 1)]['line'] === $line) {
75			return;
76			}
77
78			if (strpos($tokens[$stackPtr]['content'], " ") !== false) {
79			$error = 'Tabs must be used to indent lines; spaces are not allowed for code indentation';
80			$phpcsFile->addError($error, $stackPtr, 'SpacesUsedForIndentation');
81			}
82			}//end process()
83
84
85			}//end class
86
87			?>
			0 ignored issues – show Best Practice introduced 2017-02-07 02:10 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is not recommended to use PHP's closing tag `?>` in files other than templates. Using a closing tag in PHP files that only contain PHP code is not recommended as you might accidentally add whitespace after the closing tag which would then be output by PHP. This can cause severe problems, for example headers cannot be sent anymore. A simple precaution is to leave off the closing tag as it is not required, and it also has no negative effects whatsoever. Loading history... Coding Style introduced 2017-02-07 02:10 UTC by Report Bug Copy Issue Report Show Similar Issues like this As per coding style, files should not end with a newline character. This check marks files that end in a newline character, i.e. an empy line. Loading history...
88

timw4mail / HummingBirdAnimeClient

Issues (287)

Security Analysis not enabled

Sniffs/WhiteSpace/DisallowSpaceIndentSniff.php (2 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like