Is this repo still maintained?

[superlazyname]

Hello, what is the status of this repository's support?

• Is RedHat supporting this project? Seems like a lot of issues are getting autoclosed by a bot without much response.
• What version of upstream oauth2-proxy is this based on?
• There have been security vulnerabilities in oauth2-proxy's code that have been fixed in https://github.com/oauth2-proxy/oauth2-proxy , which of those vulnerabilities affect this fork? Have they been fixed?
• It looks like this project was forked from https://github.com/bitly/oauth2_proxy but that's been archived since 2019
• The version of Go used in this project (1.20) has been EOL since February
• govulncheck reports that the version of /net that's in use is vulnerable to https://pkg.go.dev/vuln/GO-2024-2687, and otelgrpc is vulnerable to https://pkg.go.dev/vuln/GO-2023-2331

[ibihim]

Hey,

thank you for your reasonable questions. The project has not a very high priority on our agenda compared to other topics and we are moving our focus on kube-rbac-proxy.

We will try to bump its deps and everything once the PR to fix the e2e-component tests merges.

The image that is being created within openshift is usually managed by the ART team. AFAIK it is independent of what is in the repository's .ci-operator.yaml. What they actually use, they let you know by creating PRs against the release / master branches. We were not able to merge them because of the failing test above and a lack of priority.