Project maintenance status inquiry

[ilogus]

Hello 👋

I'd like to ask about the current status of this project.

Is there a plan to maintain it or keep it updated in the future? Alternatively, is someone expected to take over its maintenance?

Thank you for any clarification!

[MedAziz11]

Hi! Thanks so much for your interest in UptimeKumaWebAPI. I’m currently quite busy with work and studies, so I haven’t been able to actively maintain or update it.

I’d definitely be open to sharing access with another maintainer to help keep the project going. If you're interested in contributing or taking a more active role, feel free to let me know what you'd like to work on, and we can arrange collaborator access.

Thanks again for reaching out!

[ilogus]

Hello @MedAziz11 Thanks a lot for your reply!

I'm not a Python expert at all 😅 I cannot take on this responsibility.

But I could read on this issue #81 that @021-projects (https://github.com/021-projects/Uptime-Kuma-Web-API/tree/develop) already proposed himself to maintain this project.

[021-projects]

@MedAziz11, I confirm - I am ready to take support for this repository :)
I will contact you by mail soon

[MedAziz11]

@MedAziz11, I confirm - I am ready to take support for this repository :) I will contact you by mail soon

Hi! Thanks again for your contributions and initiative with the project. I’d be happy to add you as a collaborator so you can continue contributing directly.

I’m also planning to get back on track with the project in the near future. Thanks for your understanding and support!

[nickorr]

@021-projects : I can see your fork didn't get updated, have you heard from @MedAziz11 about taking over yet?

The pull requests here all seem fairly straight forward so I'm wondering if it's worth me doing a fork with those changes myself, or if someone else will take them on here or not.

I also noted that @monishrajkumar did a fork and updated a bunch of library versions, and @maciejbrylewicz also did a heap of what looks like good work, including tests.

I'm also keen to test and get this working on v2 now that it's out.

[021-projects]

@021-projects : I can see your fork didn't get updated, have you heard from @MedAziz11 about taking over yet?

The pull requests here all seem fairly straight forward so I'm wondering if it's worth me doing a fork with those changes myself, or if someone else will take them on here or not.

I also noted that @monishrajkumar did a fork and updated a bunch of library versions, and @maciejbrylewicz also did a heap of what looks like good work, including tests.

I'm also keen to test and get this working on v2 now that it's out.

Hi! Yes, I have been added as a contributor to this repository, but I am going through a rather difficult period in real life and have no time for open source. At the same time, develop branch already contains most of the fixes proposed in the repository and even more - for example, a fix for a performance issue. The only problem is it doesn't have a docker image. If you are planning to make a fork, do it from the develop branch and send your pull requests - I or @MedAziz11 will try to review them :)

[nickorr]

@021-projects Sorry to hear you're going through things, I hope there's light at the end of the tunnel there. Best wishes.

Thanks, I'll start on the dev branch and then see what I can contribute - I don't know much python but will see I can do.

[021-projects]

@021-projects Sorry to hear you're going through things, I hope there's light at the end of the tunnel there. Best wishes.

It’s okay, typical difficulties for a citizen of a country mired in war and corruption 😆
Thank you for your wishes) By the way, if you want to help me, you can share my web studio with someone) https://studio.gnz.is/

[nickorr]

Hi! Yes, I have been added as a contributor to this repository, but I am going through a rather difficult period in real life and have no time for open source. At the same time, develop branch already contains most of the fixes proposed in the repository and even more - for example, a fix for a performance issue. The only problem is it doesn't have a docker image. If you are planning to make a fork, do it from the develop branch and send your pull requests - I or @MedAziz11 will try to review them :)

@021-projects So I did some testing, I'm on UptimeKuma 2.0.2 running in docker using image: louislam/uptime-kuma:2 and I added this repo via image: medaziz11/uptimekuma_restapi:dev. I wasn't sure if that was up to date or not.

I seem to get a failure on first connection to the login/access-token endpoint. Sometimes only the first time, but it has taken two attempts. The logs in docker don't show much:

uptime-kuma-mm-api  | [2025-11-26 23:51:56 +0000] [7] [CRITICAL] 

Which isn't much help. The response is equally sparse with some json and a "detail" of an empty string.

I've only so far tested with GET and POST for Monitors, but will keep going. So far it's working. I'll report any more changes. I have time to fiddle and test things if there's specific things that it would be helpful to test.