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/AjaxValidator.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
 * Created by PhpStorm.
4
 * User: cals
5
 * Date: 16-12-13
6
 * Time: 下午12:31
7
 */
8
9
namespace Cals\Validator;
10
11
use Validator;
12
use Illuminate\Http\JsonResponse;
13
14
class AjaxValidator
15
{
16
    /**
17
     * Validate the values use Validator.
18
     *
19
     * @param array $values
20
     * @param $resource
21
     * @param array $messages
22
     * @param bool $sometimes
23
     */
24
    public function validate(array $values = [], $resource, array $messages = [], $sometimes = false)
25
    {
26
        $rules = $this->rules($resource);
27
        $messages = $this->messages($messages);
28
        $attributes = $this->attributes($resource);
29
        $validator = Validator::make($values, $rules, $messages, $attributes);
30
        if ($sometimes) {
31
            $extraRules = $this->rules('sometimes' . $resource);
32
            $validator->sometimes(array_keys($extraRules), $extraRules, function () use ($sometimes) {
33
                return $sometimes;
34
            });
35
        }
36
        if ($validator->fails()) {
37
            (new JsonResponse(null, 422))
38
                ->header('Access-Control-Allow-Origin', '*')
39
                ->header('Access-Control-Allow-Methods', '*')
40
                ->setData(['errors' => $validator->errors()])
41
                ->send();
42
            exit(0);
0 ignored issues
show
Coding Style Compatibility introduced by
The method validate() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
43
        }
44
    }
45
46
    /**
47
     * Get rules from validator.php.
48
     *
49
     * @param $index
50
     * @return mixed
51
     */
52
    private function rules($index)
53
    {
54
        return config('validator.rules.' . $index);
55
    }
56
57
    /**
58
     * Get messages from validator.php.
59
     *
60
     * @param $messages
61
     * @return mixed
62
     */
63
    private function messages($messages)
64
    {
65
        if (!$messages) {
66
            return config('validator.messages');
67
        }
68
        return $messages;
69
    }
70
71
    /**
72
     * Get attributes from validator.php.
73
     *
74
     * @param $index
75
     * @return mixed
76
     */
77
    private function attributes($index)
78
    {
79
        return config('validator.attributes.' . $index);
80
    }
81
}