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

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.

includes/interface-foogallery-datasource.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
 * FooGallery Datasource interface
4
 */
5
if ( ! interface_exists( 'IFooGalleryDatasource' ) ) {
6
7
	interface IFooGalleryDatasource {
8
9
		/**
10
		 * Sets the FooGallery object we are dealing with
11
		 *
12
		 * @param $foogallery FooGallery
13
		 */
14
		public function setGallery( $foogallery );
15
16
		/**
17
		 * Returns the number of images/videos in the datasource
18
		 * @return int
19
		 */
20
		public function getCount();
21
22
		/**
23
		 * Returns an array of FooGalleryAttachments from the datasource
24
		 * @return array(FooGalleryAttachment)
0 ignored issues
show
The doc-type array(FooGalleryAttachment) could not be parsed: Expected "|" or "end of type", but got "(" at position 5. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
25
		 */
26
		public function getAttachments();
27
28
		/**
29
		 * Returns the featured FooGalleryAttachment from the datasource
30
		 * @return bool|FooGalleryAttachment
31
		 */
32
		public function getFeaturedAttachment();
33
34
		/**
35
		 * Returns a serialized string that represents the media in the datasource.
36
		 * This string is persisted when saving a FooGallery
37
		 *
38
		 * @return string
39
		 */
40
		public function getSerializedData();
41
42
		//attachment_count
43
		//attachment_id_csv
44
		//attachments
45
		//find_featured_attachment_id
46
		//featured_attachment
47
		//featured_image_html
48
	}
49
}