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.

report/.js/file.js (112 issues)

1
  $(function() {
0 ignored issues
show
Additional whitespace found at start of file
Loading history...
This file is missing a doc comment.
Loading history...
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
Expected 1 space after FUNCTION keyword; 0 found
Loading history...
2
   var $window     = $(window)
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 4 spaces, but found 3.
Loading history...
Line indented incorrectly; expected at least 4 spaces, found 3
Loading history...
3
     , $top_link   = $('#toplink')
4
     , $body       = $('body, html')
5
     , offset      = $('#code').offset().top
6
     , hidePopover = function ($target) {
7
        $target.data('popover-hover', false);
8
9
        setTimeout(function () {
0 ignored issues
show
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
10
         if (!$target.data('popover-hover')) {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 12 spaces, but found 9.
Loading history...
Line indented incorrectly; expected 12 spaces, found 9
Loading history...
Expected 1 space(s) after NOT operator; 0 found
Loading history...
11
          $target.popover('hide');
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 12 spaces, but found 10.
Loading history...
Line indented incorrectly; expected at least 16 spaces, found 10
Loading history...
12
         }
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 12 spaces, but found 9.
Loading history...
Line indented incorrectly; expected 12 spaces, found 9
Loading history...
13
        }, 300);
0 ignored issues
show
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
14
     };
15
16
   $top_link.hide().click(function(event) {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 4 spaces, but found 3.
Loading history...
Line indented incorrectly; expected at least 4 spaces, found 3
Loading history...
Opening statement of multi-line function call not indented correctly; expected 0 spaces but found 3
Loading history...
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
Expected 1 space after FUNCTION keyword; 0 found
Loading history...
17
    event.preventDefault();
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 7 spaces, but found 4.
Loading history...
Line indented incorrectly; expected at least 8 spaces, found 4
Loading history...
18
    $body.animate({scrollTop:0}, 800);
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 7 spaces, but found 4.
Loading history...
Line indented incorrectly; expected at least 8 spaces, found 4
Loading history...
There must be a single space after the colon in a property/label declaration
Loading history...
19
   });
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 4 spaces, but found 3.
Loading history...
Line indented incorrectly; expected 4 spaces, found 3
Loading history...
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
20
21
   $window.scroll(function() {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 4 spaces, but found 3.
Loading history...
Line indented incorrectly; expected at least 4 spaces, found 3
Loading history...
Opening statement of multi-line function call not indented correctly; expected 0 spaces but found 3
Loading history...
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
Expected 1 space after FUNCTION keyword; 0 found
Loading history...
22
    if($window.scrollTop() > offset) {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 7 spaces, but found 4.
Loading history...
Line indented incorrectly; expected 8 spaces, found 4
Loading history...
Expected 1 space(s) after IF keyword; 0 found
Loading history...
23
     $top_link.fadeIn();
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 7 spaces, but found 5.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 5
Loading history...
24
    } else {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 7 spaces, but found 4.
Loading history...
Line indented incorrectly; expected 8 spaces, found 4
Loading history...
25
     $top_link.fadeOut();
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 7 spaces, but found 5.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 5
Loading history...
26
    }
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 7 spaces, but found 4.
Loading history...
Line indented incorrectly; expected 8 spaces, found 4
Loading history...
27
   }).scroll();
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 4 spaces, but found 3.
Loading history...
Line indented incorrectly; expected 4 spaces, found 3
Loading history...
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
28
29
   $('.popin')
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 4 spaces, but found 3.
Loading history...
Line indented incorrectly; expected at least 4 spaces, found 3
Loading history...
30
    .popover({trigger: 'manual'})
31
    .on({
0 ignored issues
show
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
32
     'mouseenter.popover': function () {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 5.
Loading history...
Line indented incorrectly; expected 8 spaces, found 5
Loading history...
33
      var $target = $(this);
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
34
35
      $target.data('popover-hover', true);
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
36
37
      // popover already displayed
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
Coding Style Documentation introduced by
Inline comments must start with a capital letter
Loading history...
Inline comments must end in full-stops, exclamation marks, or question marks
Loading history...
38
      if ($target.next('.popover').length) {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected 12 spaces, found 6
Loading history...
39
       return;
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 7.
Loading history...
Line indented incorrectly; expected at least 16 spaces, found 7
Loading history...
40
      }
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected 12 spaces, found 6
Loading history...
41
42
      // show the popover
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
Coding Style Documentation introduced by
Inline comments must start with a capital letter
Loading history...
Inline comments must end in full-stops, exclamation marks, or question marks
Loading history...
43
      $target.popover('show');
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
44
45
      // register mouse events on the popover
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
Coding Style Documentation introduced by
Inline comments must start with a capital letter
Loading history...
Inline comments must end in full-stops, exclamation marks, or question marks
Loading history...
46
      $target.next('.popover:not(.popover-initialized)')
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
47
       .on({
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 7.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 7
Loading history...
Opening statement of multi-line function call not indented correctly; expected 4 spaces but found 7
Loading history...
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
48
        'mouseenter': function () {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 11 spaces, but found 8.
Loading history...
Line indented incorrectly; expected 16 spaces, found 8
Loading history...
49
         $target.data('popover-hover', true);
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 11 spaces, but found 9.
Loading history...
Line indented incorrectly; expected at least 20 spaces, found 9
Loading history...
50
        },
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 11 spaces, but found 8.
Loading history...
Line indented incorrectly; expected 16 spaces, found 8
Loading history...
51
        'mouseleave': function () {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 11 spaces, but found 8.
Loading history...
Line indented incorrectly; expected 12 spaces, found 8
Loading history...
52
         hidePopover($target);
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 11 spaces, but found 9.
Loading history...
Line indented incorrectly; expected at least 16 spaces, found 9
Loading history...
53
        }
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 11 spaces, but found 8.
Loading history...
Line indented incorrectly; expected 12 spaces, found 8
Loading history...
54
       })
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 7.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 7
Loading history...
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
55
       .addClass('popover-initialized');
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 7.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 7
Loading history...
56
     },
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 5.
Loading history...
Line indented incorrectly; expected 8 spaces, found 5
Loading history...
57
     'mouseleave.popover': function () {
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 5.
Loading history...
Line indented incorrectly; expected 8 spaces, found 5
Loading history...
58
      hidePopover($(this));
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 6.
Loading history...
Line indented incorrectly; expected at least 12 spaces, found 6
Loading history...
59
     }
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 8 spaces, but found 5.
Loading history...
Line indented incorrectly; expected 8 spaces, found 5
Loading history...
60
    });
0 ignored issues
show
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
61
  });
0 ignored issues
show
This line of the multi-line function call does not seem to be indented correctly. Expected 0 spaces, but found 2.
Loading history...
Line indented incorrectly; expected 0 spaces, found 2
Loading history...
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
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...
62