GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.

Issues (35)

Security Analysis    no request data  

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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.

src/command/Command.php (1 issue)

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

1
<?php
2
namespace izzum\command;
3
use izzum\command\Exception;
4
use izzum\command\ICommand;
5
6
/**
7
 * Serves as base class for all other concrete commands.
8
 * Concrete commands must implement the _execute() method.
9
 *
10
 * Intent: Encapsulate a request as an object, thereby letting you parameterize
11
 * clients with different requests, queue or log requests.
12
 *
13
 * A concrete Command (a subclass) can (and should be) injected with contextual
14
 * data via
15
 * dependency injection in the constructor
16
 *
17
 * @author Rolf Vreijdenberger
18
 * @link https://en.wikipedia.org/wiki/Command_pattern
19
 *      
20
 */
21
abstract class Command implements ICommand {
22
23
    /**
24
     * (non-PHPdoc)
25
     * 
26
     * @see \izzum\command\ICommand::execute()
27
     * @throws Exception https://en.wikipedia.org/wiki/Template_method_pattern
28
     */
29 39
    final public function execute()
30
    {
31
        try {
32 39
            $this->_execute();
33 39
        } catch(Exception $e) {
34 3
            $this->handleException($e);
35 3
            throw $e;
36 5
        } catch(\Exception $e) {
37
            // make sure we always throw the right type
38 5
            $e = new Exception($e->getMessage(), $e->getCode(), $e);
39 5
            $this->handleException($e);
40 5
            throw ($e);
41
        }
42 35
    }
43
44
    /**
45
     * hook method for logging etc.
46
     * 
47
     * @param Exception $e            
48
     */
49 5
    protected function handleException($e)
0 ignored issues
show
The parameter $e is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
50
    {
51
        // implement in subclass if needed
52 5
    }
53
54
    /**
55
     *
56
     * @throws \Exception
57
     */
58
    abstract protected function _execute();
59
60
    /**
61
     *
62
     * @return string
63
     */
64 5
    public function toString()
65
    {
66
        // includes the namespace
67 5
        return get_class($this);
68
    }
69
70 1
    public function __toString()
71
    {
72 1
        return $this->toString();
73
    }
74
}