Add Unix socket listening support for the server #31
AzurCrystalsecurity-scan.yml
on: push
backend-security
54s
frontend-security
25s
Annotations
11 errors and 1 warning
|
frontend-security
Process completed with exit code 1.
|
|
backend-security
antigravity.Client.FetchUserInfo calls http.Client.Do, which eventually calls net.LookupPort
|
|
backend-security
repository.NewS3BackupStoreFactory calls config.LoadDefaultConfig, which eventually calls net.LookupHost
|
|
backend-security
agent.Run calls http.Server.ListenAndServe, which calls net.Listen
|
|
backend-security
tlsfingerprint.HTTPProxyDialer.DialTLSContext calls net.Dialer.DialContext
|
|
backend-security
service.EmailService.sendMailPlain calls net.Dialer.Dial
|
|
backend-security
service.EmailService.TestSMTPConnectionWithConfig calls smtp.Dial, which calls net.Dial
|
|
backend-security
service.AuthService.LoginOrRegisterOAuthWithTokenPair calls mail.ParseAddress
|
|
backend-security
service.AuthService.LoginOrRegisterOAuthWithTokenPair calls mail.ParseAddress
|
|
backend-security
antigravity.Client.FetchUserInfo calls http.Client.Do, which eventually calls idna.ToASCII
|
|
backend-security
antigravity.Client.FetchUserInfo calls http.Client.Do, which eventually calls idna.Profile.ToASCII
|
|
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/
|