Bump google.golang.org/protobuf from 1.31.0 to 1.33.0 in /proxy-egress

[dependabot]

Bumps google.golang.org/protobuf from 1.31.0 to 1.33.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	golang/​go.opentelemetry.io/​otel@​v1.38.0
	golang/​github.com/​klauspost/​compress@​v1.18.0
	golang/​github.com/​go-redis/​redis/​v8@​v8.11.5
	golang/​go.opentelemetry.io/​otel/​exporters/​jaeger@​v1.17.0
	golang/​go.opentelemetry.io/​otel/​exporters/​otlp/​otlptrace/​otlptracehttp@​v1.38.0
	golang/​github.com/​golang-jwt/​jwt/​v5@​v5.3.0
	golang/​go.opentelemetry.io/​otel/​sdk@​v1.38.0
	golang/​github.com/​andybalholm/​brotli@​v1.2.0
	golang/​go.opentelemetry.io/​otel/​trace@​v1.38.0
	golang/​go.opentelemetry.io/​otel/​exporters/​stdout/​stdouttrace@​v1.38.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		golang/github.com/andybalholm/brotli@v1.2.0 has Filesystem access. Location: Package overview From: proxy-egress/go.mod → golang/github.com/andybalholm/brotli@v1.2.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/andybalholm/brotli@v1.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/go-jose/go-jose/v4@v4.1.1 has Filesystem access. Location: Package overview From: ? → golang/github.com/spf13/viper@v1.16.0 → golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.38.0 → golang/github.com/go-jose/go-jose/v4@v4.1.1 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/go-jose/go-jose/v4@v4.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/go-logr/logr@v1.4.3 has Filesystem access. Location: Package overview From: ? → golang/github.com/spf13/viper@v1.16.0 → golang/go.opentelemetry.io/otel/exporters/jaeger@v1.17.0 → golang/go.opentelemetry.io/otel@v1.38.0 → golang/go.opentelemetry.io/otel/sdk@v1.38.0 → golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.38.0 → golang/go.opentelemetry.io/otel/exporters/stdout/stdouttrace@v1.38.0 → golang/github.com/go-logr/logr@v1.4.3 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/go-logr/logr@v1.4.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/golang-jwt/jwt/v5@v5.3.0 has Filesystem access. Location: Package overview From: proxy-egress/go.mod → golang/github.com/golang-jwt/jwt/v5@v5.3.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/golang-jwt/jwt/v5@v5.3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/grpc-ecosystem/grpc-gateway/v2@v2.27.2 has Filesystem access. Location: Package overview From: ? → golang/github.com/spf13/viper@v1.16.0 → golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.38.0 → golang/github.com/grpc-ecosystem/grpc-gateway/v2@v2.27.2 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/grpc-ecosystem/grpc-gateway/v2@v2.27.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/klauspost/compress@v1.18.0 has Filesystem access. Location: Package overview From: proxy-egress/go.mod → golang/github.com/klauspost/compress@v1.18.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/klauspost/compress@v1.18.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/nxadm/tail@v1.4.8 has Filesystem access. Location: Package overview From: ? → golang/github.com/go-redis/redis/v8@v8.11.5 → golang/github.com/nxadm/tail@v1.4.8 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/nxadm/tail@v1.4.8. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/onsi/ginkgo@v1.16.5 has Filesystem access. Location: Package overview From: ? → golang/github.com/go-redis/redis/v8@v8.11.5 → golang/github.com/onsi/ginkgo@v1.16.5 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/onsi/ginkgo@v1.16.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/onsi/gomega@v1.18.1 has Filesystem access. Location: Package overview From: ? → golang/github.com/go-redis/redis/v8@v8.11.5 → golang/github.com/onsi/gomega@v1.18.1 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/onsi/gomega@v1.18.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/planetscale/vtprotobuf@v0.6.1-0.20240319094008-0393e58bdf10 has Filesystem access. Location: Package overview From: ? → golang/github.com/spf13/viper@v1.16.0 → golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.38.0 → golang/github.com/planetscale/vtprotobuf@v0.6.1-0.20240319094008-0393e58bdf10 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/planetscale/vtprotobuf@v0.6.1-0.20240319094008-0393e58bdf10. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/github.com/spiffe/go-spiffe/v2@v2.5.0 has Filesystem access. Location: Package overview From: ? → golang/github.com/spf13/viper@v1.16.0 → golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.38.0 → golang/github.com/spiffe/go-spiffe/v2@v2.5.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/spiffe/go-spiffe/v2@v2.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/go.opentelemetry.io/otel/sdk@v1.38.0 has Filesystem access. Location: Package overview From: proxy-egress/go.mod → golang/go.opentelemetry.io/otel/sdk@v1.38.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/go.opentelemetry.io/otel/sdk@v1.38.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/go.uber.org/goleak@v1.3.0 has Filesystem access. Location: Package overview From: ? → golang/github.com/spf13/viper@v1.16.0 → golang/go.opentelemetry.io/otel/sdk@v1.38.0 → golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.38.0 → golang/go.uber.org/goleak@v1.3.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/go.uber.org/goleak@v1.3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		golang/gonum.org/v1/gonum@v0.16.0 has Filesystem access. Location: Package overview From: ? → golang/github.com/spf13/viper@v1.16.0 → golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.38.0 → golang/gonum.org/v1/gonum@v0.16.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/gonum.org/v1/gonum@v0.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[dependabot]

Looks like google.golang.org/protobuf is up-to-date now, so this is no longer needed.