[Magisk] pndwal:
Not a guy... It was private test fork of vvb2060 (Xue ShanNangong, or Nangong Xueshan), one of the five current main official Magisk Devs... (Only John Wu is Male. 😜)

I think the mentality has changed somewhat from days when she was happy for it to be an alternative daily use Magisk build and scrupulously made source available either on GitHub or later as associated source code .zip, although it was always meant to be a test-bed for innovations in official Magisk*, and has delivered ground breaking commits... It used to be her personal fork, but seems recent Alpha builds are build from https://github.com/LSPosed/Magisk/commits/ , not public, rather than from her GitHub... You can see the LSP / @yujincheng08 (LoveSy, lovesykun, shanasaimoe, Shana Saimoe) Metagisk test branches where many commits currently originate however and of course if you don't trust Alpha you could fork a Metagisk test branch and build from source yourself... Eg for current WIP native bridge loaded Zygisk (with PR in official Magisk also from this Metagisk branch), see:

https://github.com/LSPosed/Metagisk/commits/zygisk

* Nb. vv's prolific contributions to Magisk over the last 3 years or so probably make up a good half of the current Magisk code and include so many early tests and first available builds adding compatibility for countless devices Incl. most MTK based devices & fixes... She has developed some initial fixes and enhancements in other test branches like Lite (for enhanced root detection bypasses) and MTK (for MediaTek compatibility fixes), but most have been tested in Alpha experimental branch. Just to mention a sampling I posted a couple of years ago: MTK compatibility, single package delivery, support for 64bit, sepolicy fixes, several isolated process fixes, fixes for UID, MicroG, process names, file based encryption, mount rules for Samsung, auto-close issues bot, reboot menu, multi-user and shared user id compatibility fixes, hidden apps, Chinese doc translations, offline restore app, unsupported environment checking, fix for apex path (a big one), permission fixes, module Installation fixes, Kotlin code cleanup, MagiskHide stopping fix, renameable App / single package Magisk archive (developed in cooperation with John).... And countless more recent commits for various devices/compatibility, new functionality and major refactoring of magiskinit injection, sepolicy rules and so on.

The mentality now seems to be to use a smaller test group (of course Alpha now uses MS App Centre both for telemetry to facilitate debugging and testing in a test pool mainly aimed at Devs and testers in the Chinese TG Alpha discussion group, many of whom contribute to LSPosed and associated projects, and for distribution/updates; App Centre allows mainland China users to get the automated updates since GitHub repos are apparently blocked for them) who are OK with telemetry (Devs received very negative responses about that from outsiders) and who simply trust the LSP associated Devs rather than to continue to supply source and accommodate the wants of 'needy' users any longer...

Notably, the Alpha builds are often available privately for days or weeks in the private discussion group (some 940 members) before they are forwarded to the public Alpha TG release channel (circa 33000 subscribers) which just seems to exist now to allow others to access it also if they wish... Of course if Canary is "cutting edge" Magisk, Alpha is "bleeding edge", and Devs are simply not going to accommodate users with issues who don't know how to rescue devices from bad builds, revert changes, downgrade etc even within the discussion group... It's for testers and mavericks after all, not a substitute Magisk fork for general users' daily use, and was never meant to be...

Do you mean a pre-rooted kernel / ROM?... Not sure why you want to do that... In my experience these often cause more issues/headaches for users than clean ROMs...

🤠 PW