View GitHub Repository app

Schedule Inspection
Subscribe

Issues (114)

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/config/assets-prod.php (2 issues)

← previous file next file →

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 
 * Configuration file for the "yii asset" console command.
4 
 * Note that in the console environment, some path aliases like '@webroot' and '@web' may not exist.
5 
 * Please define these missing path aliases.
6 
 */
7 
return [
8 
    // Adjust command/callback for JavaScript files compressing:
9 
    'jsCompressor' => 'java -jar /root/compiler.jar --js {from} --js_output_file {to}',
10 
    // Adjust command/callback for CSS files compressing:
11 
    'cssCompressor' => 'yui-compressor --type css {from} -o {to}',
12 
    // The list of asset bundles to compress:
13 
    'bundles' => [
14 
        'app\assets\AppAsset',
15 
        'app\modules\backend\assets\AdminAsset',
16 
        \dmstr\web\AdminLteAsset::className(),
17 
    ],
18 
    // Asset bundle for compression output:
19 
    'targets' => [
20 
        'frontend' => [
21 
            'class' => 'yii\web\AssetBundle',
22 
            'basePath' => '@app/../web/assets-prod',
23 
            'baseUrl' => '@web/assets-prod',
24 
            'js' => 'js/frontend-{hash}.js',
25 
            'css' => 'css/frontend-{hash}.css',
26 
            'depends' => [
27 
                // Include only 'frontend' assets:
0 ignored issues
– show
Unused Code Comprehensibility introduced by
38% 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...
28 
                'app\assets\AppAsset',
29 
            ],
30 
        ],
31 
        'backend' => [
32 
            'class' => 'yii\web\AssetBundle',
33 
            'basePath' => '@app/../web/assets-prod',
34 
            'baseUrl' => '@web/assets-prod',
35 
            'js' => 'js/backend-{hash}.js',
36 
            'css' => 'css/backend-{hash}.css',
37 
            'depends' => [
38 
                // Include only 'backend' assets:
0 ignored issues
– show
Unused Code Comprehensibility introduced by
38% 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...
39 
                'app\modules\backend\assets\AdminAsset',
40 
                \dmstr\web\AdminLteAsset::className(),
41 
            ],
42 
        ],
43 
        'all' => [
44 
            'class' => 'yii\web\AssetBundle',
45 
            'basePath' => '@app/../web/assets-prod',
46 
            'baseUrl' => '@web/assets-prod',
47 
            'js' => 'js/all-{hash}.js',
48 
            'css' => 'css/all-{hash}.css',
49 
        ],
50 
    ],
51 
    // Asset manager configuration:
52 
    'assetManager' => [
53 
        'basePath' => '/app/web/assets-prod',
54 
        'baseUrl' => '/assets-prod',
55 
    ],
56 
];
57