Forgive me. 
I can’t remember if we discussed this at the time, but does GitHub - discourse/all-the-themes · GitHub (and all-the-themes/update_from_meta.rb at main · discourse/all-the-themes · GitHub in particular) need a tweak to account for the newer Customization > Theme component category?
AI-generated summary
In a Dev category discussion titled ‘Does the ‘all-the-themes’ update need updating for theme components?’, JammyDodger raises whether the all-the-themes repository script needs updating to handle the newer #theme-component category. david confirms the need and shares a commit that addresses it. JammyDodger follows up, asking if the script still correctly excludes topics tagged with #broken or #unmaintained, since the method of signaling broken themes has changed. david clarifies that these tags are already excluded because they’re muted by default on Meta — meaning they don’t appear in topic lists for anonymous users, and thus aren’t included in the API the script uses. JammyDodger expresses relief, noting they had a ‘small panic attack’ when this was pointed out by @moin. The exchange ends on a light, appreciative note.
One other follow-up… the method of signalling one is broken changed as well. I noticed that the original url excluded subcategories (I’m assuming to exclude the ‘broken’ subcategory?). Is it fine that this doesn’t pick up on the broken, unmaintained, etc tags?
Excellent. 
Thanks for checking that all out for me. I had a small panic attack when @moin pointed it out. 