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

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/Pinterest/Endpoints/Boards.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
 * Copyright 2015 Dirk Groenen
4
 *
5
 * (c) Dirk Groenen <[email protected]>
6
 *
7
 * For the full copyright and license information, please view the LICENSE
8
 * file that was distributed with this source code.
9
 */
10
11
namespace DirkGroenen\Pinterest\Endpoints;
12
13
use DirkGroenen\Pinterest\Models\Board;
14
15
class Boards extends Endpoint {
16
17
    /**
18
     * Find the provided board
19
     *
20
     * @access public
21
     * @param  string    $board_id
22
     * @param  array     $data
23
     * @throws Exceptions/PinterestExceptions
24
     * @return Board
25
     */
26 2
    public function get($board_id, array $data = [])
27
    {
28 2
        $response = $this->request->get(sprintf("boards/%s/", $board_id), $data);
29 2
        return new Board($this->master, $response);
30
    }
31
32
    /**
33
     * Create a new board
34
     *
35
     * @access public
36
     * @param  array    $data
37
     * @throws Exceptions/PinterestExceptions
38
     * @return Board
39
     */
40 1
    public function create(array $data)
41
    {
42 1
        $response = $this->request->post("boards/", $data);
43 1
        return new Board($this->master, $response);
44
    }
45
46
    /**
47
     * Edit a board
48
     *
49
     * @access public
50
     * @param  string   $board_id
51
     * @param  array    $data
52
     * @param  string   $fields
53
     * @throws Exceptions/PinterestExceptions
54
     * @return Board
55
     */
56 1 View Code Duplication
    public function edit($board_id, array $data, $fields = null)
0 ignored issues
show
This method seems to be duplicated in 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...
57
    {
58 1
        $query = (!$fields) ? array() : array("fields" => $fields);
59
60 1
        $response = $this->request->update(sprintf("boards/%s/", $board_id), $data, $query);
61 1
        return new Board($this->master, $response);
62
    }
63
64
    /**
65
     * Delete a board
66
     *
67
     * @access public
68
     * @param  string    $board_id
69
     * @throws Exceptions/PinterestExceptions
70
     * @return boolean
71
     */
72 1
    public function delete($board_id)
73
    {
74 1
        $this->request->delete(sprintf("boards/%s/", $board_id));
75 1
        return true;
76
    }
77
}