Issues (106)

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/GitElephant/Status/Status.php (9 issues)

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
 * GitElephant - An abstraction layer for git written in PHP
5
 * Copyright (C) 2013  Matteo Giachino
6
 *
7
 * This program is free software: you can redistribute it and/or modify
8
 * it under the terms of the GNU General Public License as published by
9
 * the Free Software Foundation, either version 3 of the License, or
10
 * (at your option) any later version.
11
 *
12
 * This program is distributed in the hope that it will be useful,
13
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
14
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
15
 * GNU General Public License for more details.
16
 *
17
 * You should have received a copy of the GNU General Public License
18
 * along with this program.  If not, see [http://www.gnu.org/licenses/].
19
 */
20
21
namespace GitElephant\Status;
22
23
use GitElephant\Command\MainCommand;
24
use GitElephant\Repository;
25
use PhpCollection\Sequence;
26
27
/**
28
 * Class Status
29
 *
30
 * @package GitElephant\Status
31
 */
32
class Status
33
{
34
    /**
35
     * @var \GitElephant\Repository
36
     */
37
    private $repository;
38
39
    /**
40
     * @var array<StatusFile>
41
     */
42
    protected $files;
43
44
    /**
45
     * Private constructor in order to follow the singleton pattern
46
     *
47
     * @param Repository $repository
48
     *
49
     * @throws \RuntimeException
50
     * @throws \Symfony\Component\Process\Exception\RuntimeException
51
     */
52 10
    private function __construct(Repository $repository)
53
    {
54 10
        $this->files = [];
55 10
        $this->repository = $repository;
56 10
        $this->createFromCommand();
57 10
    }
58
59
    /**
60
     * @param Repository $repository
61
     *
62
     * @return \GitElephant\Status\Status
63
     */
64 10
    public static function get(Repository $repository)
65
    {
66 10
        return new static($repository);
67
    }
68
69
    /**
70
     * create from git command
71
     */
72 10
    private function createFromCommand(): void
73
    {
74 10
        $command = MainCommand::getInstance($this->repository)->status(true);
75 10
        $lines = $this->repository->getCaller()->execute($command)->getOutputLines(true);
76 10
        $this->parseOutputLines($lines);
77 10
    }
78
79
    /**
80
     * all files
81
     *
82
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
83
     */
84 1
    public function all(): \PhpCollection\Sequence
85
    {
86 1
        return new Sequence($this->files);
87
    }
88
89
    /**
90
     * untracked files
91
     *
92
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
93
     */
94 2
    public function untracked(): \PhpCollection\Sequence
95
    {
96 2
        return $this->filterByType(StatusFile::UNTRACKED);
97
    }
98
99
    /**
100
     * modified files
101
     *
102
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
103
     */
104 2
    public function modified(): \PhpCollection\Sequence
105
    {
106 2
        return $this->filterByType(StatusFile::MODIFIED);
107
    }
108
109
    /**
110
     * added files
111
     *
112
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
113
     */
114 4
    public function added(): \PhpCollection\Sequence
115
    {
116 4
        return $this->filterByType(StatusFile::ADDED);
117
    }
118
119
    /**
120
     * deleted files
121
     *
122
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
123
     */
124 2
    public function deleted(): \PhpCollection\Sequence
125
    {
126 2
        return $this->filterByType(StatusFile::DELETED);
127
    }
128
129
    /**
130
     * renamed files
131
     *
132
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
133
     */
134 1
    public function renamed(): \PhpCollection\Sequence
135
    {
136 1
        return $this->filterByType(StatusFile::RENAMED);
137
    }
138
139
    /**
140
     * copied files
141
     *
142
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
143
     */
144
    public function copied(): \PhpCollection\Sequence
145
    {
146
        return $this->filterByType(StatusFile::COPIED);
147
    }
148
149
    /**
150
     * create objects from command output
151
     * https://www.kernel.org/pub/software/scm/git/docs/git-status.html in the output section
152
     *
153
     *
154
     * @param array $lines
155
     */
156 10
    private function parseOutputLines(array $lines): void
157
    {
158 10
        foreach ($lines as $line) {
159 9
            $matches = $this->splitStatusLine($line);
160 9
            if ($matches) {
161 9
                $x = isset($matches[1]) ? $matches[1] : null;
162 9
                $y = isset($matches[2]) ? $matches[2] : null;
163 9
                $file = isset($matches[3]) ? $matches[3] : null;
164 9
                $renamedFile = isset($matches[5]) ? $matches[5] : null;
165
                $this->files[] = StatusFile::create($x, $y, $file, $renamedFile);
166 10
            }
167
        }
168
    }
169
170
    /**
171
     * @param string $line
172
     *
173
     * @return array<string>|null
174
     */
175
    protected function splitStatusLine(string $line)
176
    {
177
        preg_match('/^([MADRCU\? ])?([MADRCU\? ])?\ "?([^"]+?)"?( -> "?([^"]+?)"?)?$/', $line, $matches);
178
        return $matches;
179
    }
180
181
    /**
182
     * filter files status in working tree and in index status
183
     *
184
     * @param string $type
185
     *
186
     * @return Sequence<StatusFile>
0 ignored issues
show
The doc-type Sequence<StatusFile> could not be parsed: Expected "|" or "end of type", but got "<" at position 8. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
187 5
     */
188
    protected function filterByType(string $type): \PhpCollection\Sequence
189 5
    {
190
        if (!$this->files) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $this->files of type GitElephant\Status\StatusFile[] is implicitly converted to a boolean; are you sure this is intended? If so, consider using empty($expr) instead to make it clear that you intend to check for an array without elements.

This check marks implicit conversions of arrays to boolean values in a comparison. While in PHP an empty array is considered to be equal (but not identical) to false, this is not always apparent.

Consider making the comparison explicit by using empty(..) or ! empty(...) instead.

Loading history...
191
            return new Sequence();
192
        }
193 5
194 5
        return new Sequence(
195 5
            array_filter(
196
                $this->files,
197 5
                function (StatusFile $statusFile) use ($type) {
198 5
                    return $type === $statusFile->getWorkingTreeStatus() || $type === $statusFile->getIndexStatus();
199
                }
200
            )
201
        );
202
    }
203
}
204