Issues (101)

Security Analysis    not enabled

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/Migrations/Seeder.php (3 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
namespace Consigliere\Components\Migrations;
4
5
use Illuminate\Support\Collection;
6
use Consigliere\Components\Component;
7
8
class Seeder
9
{
10
    /**
11
     * Pingpong Component instance.
12
     *
13
     * @var \Consigliere\Components\Component
14
     */
15
    protected $component;
16
17
    /**
18
     * Laravel Application instance.
19
     *
20
     * @var \Illuminate\Foundation\Application.
21
     */
22
    protected $laravel;
23
24
    /**
25
     * The database connection to be used
26
     *
27
     * @var string
28
     */
29
    protected $database = '';
30
31
    /**
32
     * Create new instance.
33
     *
34
     * @param \Consigliere\Components\Component $component
35
     */
36
    public function __construct(Component $component)
37
    {
38
        $this->component = $component;
39
        $this->laravel   = $component->getLaravel();
0 ignored issues
show
Documentation Bug introduced by
It seems like $component->getLaravel() of type object<Illuminate\Foundation\Application> is incompatible with the declared type object<Illuminate\Foundation\Application.> of property $laravel.

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...
40
    }
41
42
    /**
43
     * Set the database connection to be used
44
     *
45
     * @param $database
46
     *
47
     * @return $this
48
     */
49
    public function setDatabase($database)
50
    {
51
        if (is_string($database) && $database) {
52
            $this->database = $database;
53
        }
54
    }
55
56
    /**
57
     * @return Component
58
     */
59
    public function getComponent()
60
    {
61
        return $this->component;
62
    }
63
64
    /**
65
     * Get seed path.
66
     *
67
     * @return string
68
     */
69 View Code Duplication
    public function getPath()
0 ignored issues
show
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
70
    {
71
        $config = $this->component->get('seed');
72
73
        $path = (is_array($config) && array_key_exists('path', $config)) ? $config['path'] : config('components.paths.generator.seed');
74
75
        return $this->component->getExtraPath($path);
76
    }
77
78
    /**
79
     * Get seed files.
80
     *
81
     * @param boolean $reverse
82
     *
83
     * @return array
84
     */
85 View Code Duplication
    public function getSeeds($reverse = false)
0 ignored issues
show
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
86
    {
87
        $files = $this->laravel['files']->glob($this->getPath() . '/*_*.php');
88
89
        // Once we have the array of files in the directory we will just remove the
90
        // extension and take the basename of the file which is all we need when
91
        // finding the seeds that haven't been run against the databases.
92
        if ($files === false) {
93
            return [];
94
        }
95
96
        $files = array_map(function($file) {
97
            return str_replace('.php', '', basename($file));
98
99
        }, $files);
100
101
        // Once we have all of the formatted file names we will sort them and since
102
        // they all start with a timestamp this should give us the seeds in
103
        // the order they were actually created by the application developers.
104
        sort($files);
105
106
        if ($reverse) {
107
            return array_reverse($files);
108
        }
109
110
        return $files;
111
    }
112
}
113