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

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/WorkflowInternalInterface.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
 * @link https://github.com/old-town/old-town-workflow
4
 * @author  Malofeykin Andrey  <[email protected]>
5
 */
6
namespace OldTown\Workflow;
7
8
use OldTown\Workflow\Config\ConfigurationInterface;
9
use OldTown\Workflow\Exception\FactoryException;
10
use OldTown\Workflow\Exception\InvalidArgumentException;
11
use OldTown\Workflow\Loader\WorkflowDescriptor;
12
13
/**
14
 * Interface WorkflowInternalInterface
15
 *
16
 * @package OldTown\Workflow
17
 */
18
interface WorkflowInternalInterface extends WorkflowInterface
19
{
20
    /**
21
     * Get the available actions for the specified workflow instance.
22
     * @param integer $id The workflow instance id.
23
     * @param array $inputs The inputs map to pass on to conditions
24
     * @return []
0 ignored issues
show
The doc-type [] could not be parsed: Unknown type name "" at position 0. [(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
     * @throws InvalidArgumentException if the specified id does not exist, or if its workflow
26
     * descriptor is no longer available or has become invalid.
27
     */
28
    public function getAvailableActions($id, array $inputs = []);
29
30
    /**
31
     * Set the configuration for this workflow.
32
     * If not set, then the workflow will use the default configuration static instance.
33
     * @param ConfigurationInterface $configuration a workflow configuration
34
     * @return $this
35
     */
36
    public function setConfiguration(ConfigurationInterface $configuration);
37
38
    /**
39
     * Get all available workflow names.
40
     *
41
     * @return String[]
42
     */
43
    public function getWorkflowNames();
44
45
    /**
46
     * Determine if a particular workflow can be initialized.
47
     * @param string $workflowName The workflow name to check.
48
     * @param integer $initialAction The potential initial action.
49
     * @param array $inputs The inputs to check.
50
     * @return boolean true if the workflow can be initialized, false otherwise.
51
     */
52
    //public function canInitialize($workflowName, $initialAction, array $inputs = []);
0 ignored issues
show
Unused Code Comprehensibility introduced by
60% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
53
54
    /**
55
     * Remove the specified workflow descriptor.
56
     * @param string $workflowName The workflow name of the workflow to remove.
57
     * @return boolean true if the workflow was removed, false otherwise.
58
     * @throws FactoryException If the underlying workflow factory has an error removing the workflow,
59
     * or if it does not support the removal of workflows.
60
     */
61
    public function removeWorkflowDescriptor($workflowName);
62
63
    /**
64
     * Add a new workflow descriptor
65
     * @param string $workflowName The workflow name of the workflow to add
66
     * @param WorkflowDescriptor $descriptor The workflow descriptor to add
67
     * @param boolean $replace true, if an existing descriptor should be overwritten
68
     * @return boolean true if the workflow was added, fales otherwise
69
     * @throws FactoryException If the underlying workflow factory has an error adding the workflow,
70
     * or if it does not support adding workflows.
71
     */
72
    public function saveWorkflowDescriptor($workflowName, WorkflowDescriptor $descriptor, $replace);
73
}
74