Add Redis Unix socket connection support #46
AzurCrystalsecurity-scan.yml
on: push
backend-security
43s
frontend-security
20s
Annotations
7 errors and 1 warning
|
backend-security
Process completed with exit code 3.
|
|
backend-security
service.GatewayService.Forward calls x509.HostnameError.Error
|
|
backend-security
tlsfingerprint.performTLSHandshake calls utls.UConn.HandshakeContext, which eventually calls x509.Certificate.VerifyHostname
|
|
backend-security
tlsfingerprint.performTLSHandshake calls utls.UConn.HandshakeContext, which eventually calls x509.Certificate.Verify
|
|
backend-security
service.EmailService.TestSMTPConnectionWithConfig calls smtp.NewClient, which calls textproto.Reader.ReadResponse
|
|
backend-security
tlsfingerprint.HTTPProxyDialer.DialTLSContext calls http.ReadResponse, which calls textproto.Reader.ReadMIMEHeader
|
|
backend-security
admin.SettingHandler.TestSMTPConnection calls textproto.Error.Error
|
|
frontend-security
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|