This project does not seem to handle request data directly as such no vulnerable execution paths were found.
include
, or for example
via PHP's auto-loading mechanism.
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | return [ |
||
4 | |||
5 | /* |
||
0 ignored issues
–
show
|
|||
6 | |-------------------------------------------------------------------------- |
||
7 | | Component Namespace |
||
8 | |-------------------------------------------------------------------------- |
||
9 | | |
||
10 | | Default component namespace. |
||
11 | | |
||
12 | */ |
||
13 | |||
14 | 'namespace' => 'App\Components', |
||
15 | |||
16 | /* |
||
17 | |-------------------------------------------------------------------------- |
||
18 | | Component Stubs |
||
19 | |-------------------------------------------------------------------------- |
||
20 | | |
||
21 | | Default component stubs. |
||
22 | | |
||
23 | */ |
||
24 | |||
25 | 'stubs' => [ |
||
26 | 'enabled' => false, |
||
27 | 'path' => base_path(__DIR__ . '/../src/Commands/stubs'), |
||
28 | 'files' => [ |
||
29 | 'start' => 'start.php', |
||
30 | 'routes' => 'src/Http/routes.php', |
||
31 | 'json' => 'component.json', |
||
32 | 'views/index' => 'Resources/views/index.blade.php', |
||
33 | 'views/master' => 'Resources/views/layouts/master.blade.php', |
||
34 | 'scaffold/config' => 'Config/config.php', |
||
35 | 'composer' => 'composer.json', |
||
36 | ], |
||
37 | 'replacements' => [ |
||
38 | 'start' => ['LOWER_NAME'], |
||
39 | 'routes' => ['LOWER_NAME', 'STUDLY_NAME', 'COMPONENT_NAMESPACE'], |
||
40 | 'json' => ['LOWER_NAME', 'STUDLY_NAME', 'COMPONENT_NAMESPACE'], |
||
41 | 'views/index' => ['LOWER_NAME'], |
||
42 | 'views/master' => ['STUDLY_NAME'], |
||
43 | 'scaffold/config' => ['STUDLY_NAME'], |
||
44 | 'composer' => [ |
||
45 | 'LOWER_NAME', |
||
46 | 'STUDLY_NAME', |
||
47 | 'VENDOR', |
||
48 | 'AUTHOR_NAME', |
||
49 | 'AUTHOR_EMAIL', |
||
50 | 'COMPONENT_NAMESPACE', |
||
51 | ], |
||
52 | ], |
||
53 | ], |
||
54 | 'paths' => [ |
||
55 | /* |
||
56 | |-------------------------------------------------------------------------- |
||
57 | | Components path |
||
58 | |-------------------------------------------------------------------------- |
||
59 | | |
||
60 | | This path used for save the generated component. This path also will added |
||
61 | | automatically to list of scanned folders. |
||
62 | | |
||
63 | */ |
||
64 | |||
65 | 'components' => base_path('app/Components'), |
||
66 | /* |
||
67 | |-------------------------------------------------------------------------- |
||
68 | | Components assets path |
||
69 | |-------------------------------------------------------------------------- |
||
70 | | |
||
71 | | Here you may update the components assets path. |
||
72 | | |
||
73 | */ |
||
74 | |||
75 | 'assets' => base_path('components'), |
||
76 | /* |
||
77 | |-------------------------------------------------------------------------- |
||
78 | | The migrations path |
||
79 | |-------------------------------------------------------------------------- |
||
80 | | |
||
81 | | Where you run 'component:publish-migration' command, where do you publish the |
||
82 | | the migration files? |
||
83 | | |
||
84 | */ |
||
85 | |||
86 | 'migration' => base_path('database/migrations'), |
||
87 | /* |
||
88 | |-------------------------------------------------------------------------- |
||
89 | | The seeds path |
||
90 | |-------------------------------------------------------------------------- |
||
91 | | |
||
92 | | Where you run 'component:publish-seed' command, where do you publish the |
||
93 | | the seed files? |
||
94 | | |
||
95 | */ |
||
96 | |||
97 | 'seed' => base_path('database/seeds'), |
||
98 | /* |
||
99 | |-------------------------------------------------------------------------- |
||
100 | | Generator path |
||
101 | |-------------------------------------------------------------------------- |
||
102 | | |
||
103 | | Here you may update the components generator path. |
||
104 | | |
||
105 | */ |
||
106 | 'generator' => [ |
||
107 | 'assets' => 'Resources/assets', |
||
108 | 'config' => 'Config', |
||
109 | 'command' => 'src/Console', |
||
110 | 'event' => 'src/Events', |
||
111 | 'listener' => 'src/Events/Handlers', |
||
112 | 'migration' => 'Database/Migrations', |
||
113 | 'model' => 'src/Models', |
||
114 | 'repository' => 'src/Repositories', |
||
115 | 'seed' => 'Database/Seeds', |
||
116 | 'controller' => 'src/Http/Controllers', |
||
117 | 'middleware' => 'src/Http/Middleware', |
||
118 | 'request' => 'src/Http/Requests', |
||
119 | 'provider' => 'src/Providers', |
||
120 | 'lang' => 'Resources/lang', |
||
121 | 'views' => 'Resources/views', |
||
122 | 'test' => 'Tests', |
||
123 | 'jobs' => 'src/Jobs', |
||
124 | 'emails' => 'src/Emails', |
||
125 | 'notifications' => 'src/Notifications', |
||
126 | ], |
||
127 | ], |
||
128 | /* |
||
129 | |-------------------------------------------------------------------------- |
||
130 | | Scan Path |
||
131 | |-------------------------------------------------------------------------- |
||
132 | | |
||
133 | | Here you define which folder will be scanned. By default will scan vendor |
||
134 | | directory. This is useful if you host the package in packagist website. |
||
135 | | |
||
136 | */ |
||
137 | |||
138 | 'scan' => [ |
||
139 | 'enabled' => true, |
||
140 | 'paths' => [ |
||
141 | base_path('vendor/*/*'), |
||
142 | ], |
||
143 | ], |
||
144 | /* |
||
145 | |-------------------------------------------------------------------------- |
||
146 | | Composer File Template |
||
147 | |-------------------------------------------------------------------------- |
||
148 | | |
||
149 | | Here is the config for composer.json file, generated by this package |
||
150 | | |
||
151 | */ |
||
152 | |||
153 | 'composer' => [ |
||
154 | 'vendor' => 'componentsv', |
||
155 | 'author' => [ |
||
156 | 'name' => 'anonymoussc', |
||
157 | 'email' => '[email protected]', |
||
158 | ], |
||
159 | ], |
||
160 | /* |
||
161 | |-------------------------------------------------------------------------- |
||
162 | | Caching |
||
163 | |-------------------------------------------------------------------------- |
||
164 | | |
||
165 | | Here is the config for setting up caching feature. |
||
166 | | |
||
167 | */ |
||
168 | 'cache' => [ |
||
169 | 'enabled' => false, |
||
170 | 'key' => 'componentsv', |
||
171 | 'lifetime' => 60, |
||
172 | ], |
||
173 | /* |
||
174 | |-------------------------------------------------------------------------- |
||
175 | | Choose what components will register as custom namespaces. |
||
176 | | Setting one to false will require to register that part |
||
177 | | in your own Service Provider class. |
||
178 | |-------------------------------------------------------------------------- |
||
179 | */ |
||
180 | 'register' => [ |
||
181 | 'translations' => true, |
||
182 | ], |
||
183 | /* |
||
184 | |-------------------------------------------------------------------------- |
||
185 | | Published assets merge. |
||
186 | | Published assets will merge into target assets directory or |
||
187 | | retain it's own components (as a directory) name |
||
188 | |-------------------------------------------------------------------------- |
||
189 | */ |
||
190 | 'merge' => [ |
||
191 | 'published-assets' => true, |
||
192 | ], |
||
193 | ]; |
||
194 |
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.