Interesting, never seen that one before. Will consume those lists too.
The contributors seem to be Hive account@good-karma, Hive account@therealwolf, Hive account@rishi556, Hive account@holger80, Hive account@reazuliqbal, Hive account@quochuy.

• It does not seem to be actively maintained though, those lists haven't been updated in 2.5 years (1.5 ys for bad actors and 2.5 ys for bad domains).

• Using that library, to get an updated list of known bad actors/domains requires you to pull the updated npm library and do a frontend release. Not as quick as required to counteract phishing waves.

Besides the lists of bad actors/domains in my "database", KD consumes Hive account@guiltyparties / Hive account@logic lists too:

• https://spaminator.me/api/p/domains.json
• https://raw.githubusercontent.com/gryter/plentyofphish/master/phishingurls.txt

So ideally Hive frontends should consume from all 3 sources. Or let the user decide which ones to consume from (eg. with checkboxes).

Mine is going to keep being actively maintained as it has for the past 3.5 years.
That's also because I have more development plans for this bot, as the token of my game (crypto shots) will be used to unlock premium features for this and other projects of mine in order to add utility. [spoiler 😉]