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

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/Laravel/ResponseServiceProvider.php (2 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 EllipseSynergie\ApiResponse\Laravel;
4
5
use EllipseSynergie\ApiResponse\Serializer\Serializer;
6
use Illuminate\Support\ServiceProvider;
7
use League\Fractal\Manager;
8
9
/**
10
 * Class ResponseServiceProvider
11
 *
12
 * For the full copyright and license information, please view the LICENSE
13
 * file that was distributed with this source code.
14
 *
15
 * @package EllipseSynergie\ApiResponse\Laravel
16
 * @author Maxime Beaudoin <[email protected]>
17
 */
18
class ResponseServiceProvider extends ServiceProvider
19
{
20
    /**
21
     * Register the service provider.
22
     *
23
     * @return void
24
     */
25
    public function boot()
26
    {
27
        $response = $this->bootResponse();
28
        $this->registerMacro($response);
0 ignored issues
show
Deprecated Code introduced by
The method EllipseSynergie\ApiRespo...ovider::registerMacro() has been deprecated with message: We still register macro for backward compatibility, but DO NOT USE THIS MACRO ANYMORE !

This method has been deprecated. The supplier of the class has supplied an explanatory message.

The explanatory message should give you some clue as to whether and when the method will be removed from the class and what other method or class to use instead.

Loading history...
29
    }
30
31
    /**
32
     * Override this to use your own serializer.
33
     *
34
     * @return Serializer
35
     */
36
    protected function getSerializer()
37
    {
38
        return new Serializer();
39
    }
40
41
    /**
42
     * Boot response
43
     *
44
     * @return Response
45
     */
46
    protected function bootResponse()
47
    {
48
        $manager = new Manager;
49
50
        // Custom serializer because DataArraySerializer doesn't provide the opportunity to change the resource key
51
        $manager->setSerializer($this->getSerializer());
52
53
        //Get includes from request
54
        $includes = $this->app['Illuminate\Http\Request']->get('include');
55
56
        //If includes is not already a array
57
        if(!is_array($includes)){
58
            $includes = explode(',', $includes);
59
        }
60
61
        // Are we going to try and include embedded data?
62
        $manager->parseIncludes($includes);
63
64
        // Return the Response object
65
        $response = new Response($manager);
66
67
        //Set the response instance properly
68
        $this->app->instance('EllipseSynergie\ApiResponse\Contracts\Response', $response);
69
70
        return $response;
71
    }
72
73
    /**
74
     * Register the service provider.
75
     *
76
     * @return void
77
     */
78
    public function register()
79
    {
80
        //
81
    }
82
83
    /**
84
     * Register response macro
85
     *
86
     * @deprecated We still register macro for backward compatibility, but DO NOT USE THIS MACRO ANYMORE !
87
     * @param Response $response
88
     */
89
    private function registerMacro($response)
90
    {
91
        \Response::macro('api', function () use ($response) {
0 ignored issues
show
The method macro() does not seem to exist on object<Illuminate\Contra...outing\ResponseFactory>.

This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.

This is most likely a typographical error or the method has been renamed.

Loading history...
92
            return $response;
93
        });
94
    }
95
}
96