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 (57)

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/JonnyW/PhantomJs/Procedure/Output.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
3
/*
4
 * This file is part of the php-phantomjs.
5
 *
6
 * For the full copyright and license information, please view the LICENSE
7
 * file that was distributed with this source code.
8
 */
9
10
namespace JonnyW\PhantomJs\Procedure;
11
12
/**
13
 * PHP PhantomJs
14
 *
15
 * @author Jon Wenmoth <[email protected]>
16
 */
17
class Output implements OutputInterface
18
{
19
    /**
20
     * Output data.
21
     *
22
     * @var array
23
     * @access protected
24
     */
25
    protected $data;
26
27
    /**
28
     * Output logs.
29
     *
30
     * @var array
31
     * @access protected
32
     */
33
    protected $logs;
34
35
    /**
36
     * Internal constructor.
37
     *
38
     * @access public
39
     * @return void
0 ignored issues
show
Comprehensibility Best Practice introduced by
Adding a @return annotation to constructors is generally not recommended as a constructor does not have a meaningful return value.

Adding a @return annotation to a constructor is not recommended, since a constructor does not have a meaningful return value.

Please refer to the PHP core documentation on constructors.

Loading history...
40
     */
41 22
    public function __construct()
42
    {
43 22
        $this->data = array();
44 22
        $this->logs = array();
45 22
    }
46
47
    /**
48
     * Import data.
49
     *
50
     * @param array $data
51
     * @access public
52
     */
53 18
    public function import(array $data)
54
    {
55 18
        $this->data = $data;
56 18
    }
57
58
    /**
59
     * Set data value.
60
     *
61
     * @access public
62
     * @param  string                             $name
63
     * @param  mixed                              $value
64
     * @return \JonnyW\PhantomJs\Procedure\Output
65
     */
66 1
    public function set($name, $value)
67
    {
68 1
        $this->data[$name] = $value;
69
70 1
        return $this;
71
    }
72
73
    /**
74
     * Get data value.
75
     *
76
     * @access public
77
     * @param  string $name
78
     * @return mixed
79
     */
80 19
    public function get($name)
81
    {
82 19
        if (isset($this->data[$name])) {
83 6
            return $this->data[$name];
84
        }
85
86 13
        return '';
87
    }
88
89
    /**
90
     * Log data.
91
     *
92
     * @access public
93
     * @param string $data
94
     */
95 1
    public function log($data)
96
    {
97 1
        $this->logs[] = $data;
98 1
    }
99
100
    /**
101
     * Get log data.
102
     *
103
     * @access public
104
     * @return array
105
     */
106 1
    public function getLogs()
107
    {
108 1
        return $this->logs;
109
    }
110
}
111