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

config/session.php (1 issue)

Severity
1
<?php
2
3
return [
4
    /*
5
    |--------------------------------------------------------------------------
6
    | Default Session Driver
7
    |--------------------------------------------------------------------------
8
    |
9
    | This option controls the default session "driver" that will be used on
10
    | requests. By default, we will use the lightweight native driver but
11
    | you may specify any of the other wonderful drivers provided here.
12
    |
13
    | Supported: "file", "cookie", "database", "apc",
14
    |            "memcached", "redis", "array"
15
    |
16
    */
17
18
    'driver' => env('SESSION_DRIVER', 'file'),
19
20
    /*
21
    |--------------------------------------------------------------------------
22
    | Session Lifetime
23
    |--------------------------------------------------------------------------
24
    |
25
    | Here you may specify the number of minutes that you wish the session
26
    | to be allowed to remain idle before it expires. If you want them
27
    | to immediately expire on the browser closing, set that option.
28
    |
29
    */
30
31
    'lifetime' => env('SESSION_LIFETIME', 120),
32
33
    'expire_on_close' => false,
34
35
    /*
36
    |--------------------------------------------------------------------------
37
    | Session Encryption
38
    |--------------------------------------------------------------------------
39
    |
40
    | This option allows you to easily specify that all of your session data
41
    | should be encrypted before it is stored. All encryption will be run
42
    | automatically by Laravel and you can use the Session like normal.
43
    |
44
    */
45
46
    'encrypt' => false,
47
48
    /*
49
    |--------------------------------------------------------------------------
50
    | Session File Location
51
    |--------------------------------------------------------------------------
52
    |
53
    | When using the native session driver, we need a location where session
54
    | files may be stored. A default has been set for you but a different
55
    | location may be specified. This is only needed for file sessions.
56
    |
57
    */
58
59
    'files' => storage_path('framework/sessions'),
60
61
    /*
62
    |--------------------------------------------------------------------------
63
    | Session Database Connection
64
    |--------------------------------------------------------------------------
65
    |
66
    | When using the "database" or "redis" session drivers, you may specify a
67
    | connection that should be used to manage these sessions. This should
68
    | correspond to a connection in your database configuration options.
69
    |
70
    */
71
72
    'connection' => null,
73
74
    /*
75
    |--------------------------------------------------------------------------
76
    | Session Database Table
77
    |--------------------------------------------------------------------------
78
    |
79
    | When using the "database" session driver, you may specify the table we
80
    | should use to manage the sessions. Of course, a sensible default is
81
    | provided for you; however, you are free to change this as needed.
82
    |
83
    */
84
85
    'table' => 'sessions',
86
87
    /*
88
    |--------------------------------------------------------------------------
89
    | Session Cache Store
90
    |--------------------------------------------------------------------------
91
    |
92
    | When using the "apc" or "memcached" session drivers, you may specify a
93
    | cache store that should be used for these sessions. This value must
94
    | correspond with one of the application's configured cache stores.
95
    |
96
    */
97
98
    'store' => null,
99
100
    /*
101
    |--------------------------------------------------------------------------
102
    | Session Sweeping Lottery
103
    |--------------------------------------------------------------------------
104
    |
105
    | Some session drivers must manually sweep their storage location to get
106
    | rid of old sessions from storage. Here are the chances that it will
107
    | happen on a given request. By default, the odds are 2 out of 100.
108
    |
109
    */
110
111
    'lottery' => [2, 100],
112
113
    /*
114
    |--------------------------------------------------------------------------
115
    | Session Cookie Name
116
    |--------------------------------------------------------------------------
117
    |
118
    | Here you may change the name of the cookie used to identify a session
119
    | instance by ID. The name specified here will get used every time a
120
    | new session cookie is created by the framework for every driver.
121
    |
122
    */
123
124
    'cookie' => env(
125
        'SESSION_COOKIE',
126
        str_slug(env('APP_NAME', 'laravel'), '_').'_session'
0 ignored issues
show
Deprecated Code introduced by
The function str_slug() has been deprecated: Str::slug() should be used directly instead. Will be removed in Laravel 5.9. ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-deprecated  annotation

126
        /** @scrutinizer ignore-deprecated */ str_slug(env('APP_NAME', 'laravel'), '_').'_session'

This function has been deprecated. The supplier of the function has supplied an explanatory message.

The explanatory message should give you some clue as to whether and when the function will be removed and what other function to use instead.

Loading history...
127
    ),
128
129
    /*
130
    |--------------------------------------------------------------------------
131
    | Session Cookie Path
132
    |--------------------------------------------------------------------------
133
    |
134
    | The session cookie path determines the path for which the cookie will
135
    | be regarded as available. Typically, this will be the root path of
136
    | your application but you are free to change this when necessary.
137
    |
138
    */
139
140
    'path' => '/',
141
142
    /*
143
    |--------------------------------------------------------------------------
144
    | Session Cookie Domain
145
    |--------------------------------------------------------------------------
146
    |
147
    | Here you may change the domain of the cookie used to identify a session
148
    | in your application. This will determine which domains the cookie is
149
    | available to in your application. A sensible default has been set.
150
    |
151
    */
152
153
    'domain' => env('SESSION_DOMAIN', null),
154
155
    /*
156
    |--------------------------------------------------------------------------
157
    | HTTPS Only Cookies
158
    |--------------------------------------------------------------------------
159
    |
160
    | By setting this option to true, session cookies will only be sent back
161
    | to the server if the browser has a HTTPS connection. This will keep
162
    | the cookie from being sent to you if it can not be done securely.
163
    |
164
    */
165
166
    'secure' => env('SESSION_SECURE_COOKIE', false),
167
168
    /*
169
    |--------------------------------------------------------------------------
170
    | HTTP Access Only
171
    |--------------------------------------------------------------------------
172
    |
173
    | Setting this value to true will prevent JavaScript from accessing the
174
    | value of the cookie and the cookie will only be accessible through
175
    | the HTTP protocol. You are free to modify this option if needed.
176
    |
177
    */
178
179
    'http_only' => true,
180
181
    /*
182
    |--------------------------------------------------------------------------
183
    | Same-Site Cookies
184
    |--------------------------------------------------------------------------
185
    |
186
    | This option determines how your cookies behave when cross-site requests
187
    | take place, and can be used to mitigate CSRF attacks. By default, we
188
    | do not enable this as other CSRF protection services are in place.
189
    |
190
    | Supported: "lax", "strict"
191
    |
192
    */
193
194
    'same_site' => null,
195
];
196