Doesn't it feel sketchy to run a terminal that isn't even packaged by Debian? I run a few non-packaged things, but I don't want my terminal, or shell, or kernel to be "some code from a some person on github".
Idk man, this is a successful project that's half a decade old[1], has over 40k stars, is wildly popular in eg. the UnixPorn and TWM communities, and is packaged by most other distros; I don't really see any cause for concern ¯\_(ツ)_/¯
That's strange. I wonder why debian is lagging behind on packaging it? Alacritty is packaged by my package manager, so I never really thought about it much.
In addition, at some point I had a look, and the former terminal I used to use (termite[0]) deprecated itself in favour of alacritty as well so I can't even switch back (I mean I could, but it's now unmaintained.)
No, not being included in Debian reflects poorly on the software. It implies there's something "wrong" with it. Perhaps it's too new, or too arcane, or in some other fashion doesn't live up to the operating system's extremely high quality and security standards.
I don't think this would necessarily be true with other Linux based operating systems (perhaps RHEL), but certainly is true in this case.
[1]: Dated via the dev's release blog post: https://jwilm.io/blog/announcing-alacritty/