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

Security Analysis    no request data  

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  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.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  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.
  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.
  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.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
  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.
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  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.
  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.
  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.
  Header Injection
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/Libraries/Config/Config.php (28 issues)

1
<?php
0 ignored issues
show
Class found in ".php" file; use ".inc" extension instead
Loading history...
This file is missing a doc comment.
Loading history...
The PHP open tag does not have a corresponding PHP close tag
Loading history...
Filename "Config.php" doesn't match the expected filename "config.php"
Loading history...
2
0 ignored issues
show
Missing file doc comment
Loading history...
3
namespace RattfieldNz\Shodan\Libraries\Config;
4
5
/**
6
 * Class Config.
7
 *
8
 * @category PHP
0 ignored issues
show
Coding Style Documentation introduced by
@category tag is not allowed in class comment
Loading history...
9
 *
10
 * @author  Rob Attfield <[email protected]>
0 ignored issues
show
Coding Style Documentation introduced by
@author tag is not allowed in class comment
Loading history...
11
 * @license https://github.com/rattfieldnz/shodan/blob/master/LICENSE MIT
0 ignored issues
show
Coding Style Documentation introduced by
@license tag is not allowed in class comment
Loading history...
12
 */
0 ignored issues
show
Missing @package tag in class comment
Loading history...
Missing @link tag in class comment
Loading history...
13
class Config
14
{
0 ignored issues
show
Opening brace should be on the same line as the declaration for class Config
Loading history...
15
    // Default timeout for API call.
16
    public const DEFAULT_TIMEOUT = 10;
17
18
    /**
19
     * Retrieve the Shodan API key.
20
     *
21
     * @return mixed|string|null The Google API key.
22
     */
23 5
    public static function shodanApiKey()
0 ignored issues
show
Expected 2 blank lines before function; 1 found
Loading history...
24
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
25 5
        $key = config('shodan.shodan.api_key');
26
27 5
        return !empty($key) ? $key : null;
0 ignored issues
show
Expected 1 space(s) after NOT operator; 0 found
Loading history...
Inline IF statements are not allowed
Loading history...
TRUE, FALSE and NULL should be uppercase as per the configured coding-style; instead of null please use NULL.
Loading history...
28
    }
0 ignored issues
show
Expected 2 blank lines after function; 1 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end shodanApiKey()
Loading history...
29
30
    /**
31
     * Retrieve set CURL timeout from config, in seconds.
32
     *
33
     * @return int CURL timeout. Default is 10.
0 ignored issues
show
Expected "integer" but found "int" for function return type
Loading history...
34
     */
35 1
    public static function curlTimeout(): int
36
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
37 1
        $timeout = config('shodan.shodan.timeout');
38
39 1
        return !empty($timeout) ? intval($timeout) : self::DEFAULT_TIMEOUT;
0 ignored issues
show
Expected 1 space(s) after NOT operator; 0 found
Loading history...
Inline IF statements are not allowed
Loading history...
40
    }
0 ignored issues
show
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end curlTimeout()
Loading history...
Expected 2 blank lines after function; 0 found
Loading history...
41
}
0 ignored issues
show
Expected //end class
Loading history...
As per coding style, files should not end with a newline character.

This check marks files that end in a newline character, i.e. an empy line.

Loading history...
42