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

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/RackspaceLogParser.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
namespace SkylerKatz\RackspaceLogParser;
4
5
class RackspaceLogParser
6
{
7
    /**
8
     * Rexeg Pattern to match Rackspace Cloud Files Logs.
9
     */
10
    const PATTERN = '/^([^ ]+) ([^ ]+) ([^ ]+) (\[[^\]]+\]) "(.*) (.*) (.*)" ([0-9\-]+) ([0-9\-]+) "(.*)" "(.*)/m';
11
12
    /**
13
     * Max Buffer size for reading log file.
14
     */
15
    const BUFFER_SIZE = 4096;
16
17
    /**
18
     * The path to the log file.
19
     *
20
     * @var string
21
     */
22
    protected $path;
23
24
    /**
25
     * The log file in memory.
26
     *
27
     * @var string
28
     */
29
    protected $log;
30
31
    /**
32
     * Create a new RackspaceLogParser Instance.
33
     *
34
     * @param string $path
35
     */
36
    public function __construct($path)
37
    {
38
        $this->path = $path;
39
        $this->processLog();
40
    }
41
42
    /**
43
     * Parse a log file into an arrray of LogItems.
44
     *
45
     * @return array
46
     */
47
    public function parse()
48
    {
49
        $entries = [];
50
51
        foreach ($this->getLogRows() as $row) {
52
            $entry = $this->parseRow($row);
53
            $entries[] = $this->createLogItem($entry);
54
        }
55
56
        return $entries;
57
    }
58
59
    /**
60
     * read a log file into memory.
61
     *
62
     * @return void
63
     */
64
    private function processLog()
65
    {
66
        // Open our file in binary mode
67
        $file = gzopen($this->path, 'rb');
68
69
        // Keep repeating until the end of the input file
70
        $log = '';
71
        while (! gzeof($file)) {
72
            $log .= gzread($file, self::BUFFER_SIZE);
73
        }
74
75
        // File is done, close files
76
        gzclose($file);
77
78
        $this->log = $log;
79
80
        return $this;
81
    }
82
83
    /**
84
     * Get the rows of a log.
85
     *
86
     * @return array
87
     */
88
    private function getLogRows()
89
    {
90
        return array_filter(explode(PHP_EOL, $this->log));
91
    }
92
93
    /**
94
     * Parse a row into its component parts.
95
     *
96
     * @param string $row
97
     * @return array
98
     */
99
    private function parseRow($row)
100
    {
101
        preg_match(self::PATTERN, $row, $entry);
102
103
        return $entry;
104
    }
105
106
    /**
107
     * Create a Log Item from a parsed log row.
108
     *
109
     * @param array $entry
110
     * @return LogItem
111
     */
112
    private function createLogItem($entry)
113
    {
114
        $logItem = new LogItem();
115
        $logItem->raw = $entry[0];
116
        $logItem->clientIp = $entry[1];
117
        $logItem->accessDate = $this->parseDate($entry[4]);
0 ignored issues
show
Documentation Bug introduced by
It seems like $this->parseDate($entry[4]) of type object<Carbon\Carbon> is incompatible with the declared type object<SkylerKatz\Racksp...ogParser\Carbon\Carbon> of property $accessDate.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
118
        $logItem->method = $entry[5];
119
        $logItem->request = $entry[6];
120
        $logItem->httpVersion = $entry[7];
121
        $logItem->returnCode = intval($entry[8]);
122
        $logItem->bytesSent = intval($entry[9]);
123
124
        $logItem->referrer = $entry[10] == '-' ? null : $entry[10];
125
        $logItem->userAgent = $entry[11];
126
127
        return $logItem;
128
    }
129
130
    /**
131
     * Parse a log date.
132
     *
133
     * @param string $date
134
     * @return \Carbon\Carbon
135
     */
136
    private function parseDate($date)
137
    {
138
        $accessDate = str_replace('[', '', $date);
139
        $accessDate = str_replace(']', '', $accessDate);
140
        $accessDate = explode(' ', $accessDate);
141
142
        return \Carbon\Carbon::createFromFormat('d/m/Y:H:i:s', $accessDate[0], new \DateTimeZone('UTC'));
143
    }
144
}
145