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

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/Constraint/DateConstraint.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
/**
4
 * @file
5
 * Class DateConstraint
6
 */
7
8
namespace Roomify\Bat\Constraint;
9
10
use Roomify\Bat\Calendar\CalendarResponse;
11
use Roomify\Bat\Constraint\Constraint;
12
13
/**
14
 * The DateConstraint provides a generalized constraint on the start and end time
15
 * of an event.
16
 *
17
 * An applicable scenario is to allow units to declare (independently of
18
 * their actual event state) whether they should be deemed as matching a search
19
 * based on the dates of the search. For example, a hotel room can declare that it
20
 * should be unavailable if the check-in time is not at least 2 days away from the
21
 * today.
22
 */
23
class DateConstraint extends Constraint {
24
25
  // The constraint start date - if on or after requested start date constraint will apply.
26
  public $start_date;
27
28
  // The constraint end date - if on or after requested end date constraint will apply.
29
  public $end_date;
30
31
  /**
32
   * DateConstraint constructor.
33
   * @param array $units
34
   * @param null $start_date
35
   * @param null $end_date
36
   */
37
  public function __construct($units, $start_date = NULL, $end_date = NULL) {
38
    parent::__construct($units);
39
40
    $this->start_date = $start_date;
41
    $this->end_date = $end_date;
42
  }
43
44
  /**
45
   * {@inheritdoc}
46
   */
47
  public function applyConstraint(CalendarResponse &$calendar_response) {
48
    parent::applyConstraint($calendar_response);
49
50
    if ($this->start_date === NULL) {
51
      $this->start_date = new \DateTime('1970-01-01');
52
    }
53
    if ($this->end_date === NULL) {
54
      $this->end_date = new \DateTime('2999-12-31');
55
    }
56
57
    // If the constraint start date is on or after the requested start date
58
    // or the constraint end date is on or before the requested end date, mark
59
    // the units as invalid.
60
    if ($this->start_date->getTimestamp() >= $calendar_response->getStartDate()->getTimestamp() ||
61
        $this->end_date->getTimestamp() <= $calendar_response->getEndDate()->getTimestamp()) {
62
63
      $units = $this->getUnits();
64
65
      $included_set = $calendar_response->getIncluded();
66
67 View Code Duplication
      foreach ($included_set as $unit_id => $set) {
0 ignored issues
show
This code seems to be duplicated across 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...
68
        if (isset($units[$unit_id]) || empty($units)) {
69
          $calendar_response->removeFromMatched($included_set[$unit_id]['unit'], CalendarResponse::CONSTRAINT, $this);
70
71
          $this->affected_units[$unit_id] = $included_set[$unit_id]['unit'];
72
        }
73
      }
74
    }
75
  }
76
77
  /**
78
   * Generates a text describing an availability_constraint.
79
   *
80
   * @return string
81
   *   The formatted message.
82
   */
83
  public function toString() {
84
    $text = '';
85
    $args = array();
86
87
    $start_date = FALSE;
88
    $end_date = FALSE;
89
90
    // Date range constraint variables.
91
    if ($this->start_date !== NULL) {
92
      $start_date = $this->start_date->format('Y-m-d');
93
    }
94
    if ($this->start_date !== NULL) {
95
      $end_date = $this->end_date->format('Y-m-d');
96
    }
97
98
    // Specify a date range constraint.
99 View Code Duplication
    if ($start_date && $end_date) {
0 ignored issues
show
This code seems to be duplicated across 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...
100
      $text = 'From @start_date to @end_date';
101
102
      $args['@start_date'] = $start_date;
103
      $args['@end_date'] = $end_date;
104
    }
105
106
    // Specify the start/end constraint.
107
    if ($start_date && $end_date) {
108
      $text = 'From @start_date to @end_date';
109
    }
110
111
    return array('text' => $text, 'args' => $args);
112
  }
113
114
}
115