Flole
Well, I don't see anything there that says they are or aren't supported. In any case there are just under 5000 packages on cloudsmith.io spanning numerous hardware and OS platforms; there is also no reasonable way to search this list, since only the last filter option is used. A good package may be there, but it's a veritable needle in a haystack.
As far as walking around and fixing broken packages, well, if one finds a bug and has a proposed solution to outside software, it behooves them to pass that on to the relevant team. This then becomes a muilti-way reciprocal arrangement, resulting in less overall effort being spent addressing issues across all organizations.
If it's connected to one's own software (e.g., some level integration), then one should ask questions about their own software, such as "How could my software better handle such problems in the future (solve them, capture contextual information surrounding the error, minimize any damage?" These are the sorts of things that good professional developers do to improve their work, which also increases efficiency.
Now one thing which may have come out of this, if what @DeltaMikeCharlie is accurate, someone in the chain between tvheadend and snap has created an undifferentiated fork of the software. The Perl modules in question were invoked internal to tvheadend, not part of the packaging, and if Perl is not used in the supported tvheadend version, then the existence of the fork needs to be highlighted and addressed.
