Problem with Apple is that they're trying very hard to control use of their stuff - so working with their stuff is very annoying. I only recently looked into it again as it was required for work projects where acquiring relevant hardware wasn't a problem - and even then it still is very annoying to manage, compared to Linux and even Windows.
I used to run cross compile setups for a bunch of open source projects 10-15 years ago, including MacOS. Back then they were using a gcc based toolchain, and thanks to GPL had to publish the base toolchain - yet they still tried very hard to break things between releases, which eventually got so bad that we decided to first drop MacOS builds, and later just completely drop MacOS support as you can't really do that without proper hardware access.
The situation has gotten a lot worse since LLVM - which Apple was pushing in big part as it allowed them to publish their SDKs under their licenses only. So nowadays you still can download their SDK - but using it on non-Apple-silicon is against their TOS.
Yeah, I assumed you meant the master password to the password manager.
Still, that falls under the duty of the page I'm visiting to keep their stuff secure - and while I'm very unhappy about some recent practices¹ I'd more for documenting and battling it out in court, if necessary.
¹ My browser configuration used to prevent 3rd party iframes or similar constructs for entering passwords - unfortunately in recent years some idiots decided that's good design, so more and more often you nowadays have to allow embedding third party components without it being visible where it comes from.
Even worse, quite often credit card verification or other payment forms get embedded the same way. Until a few years ago my bank was throwing errors in their forms when they got embedded this way, but unfortunately they caved in to the general idiocy out there, and allow that nowadays.