Uh-oh. I'm a long-term Toolbox-tinker.

I'm here on this Post, because a while back I noticed Toolbox was no longer in the Repository. I knew that could spell 'trouble'. Thanks for the 'Retired' link ... but all that's there is the link to its unpronounceable replacement-project on GitHub.

WordPress Repositories are a Very Good Thing. Indeed; being listed on the repository is a good first approximation of "Compliance Check Number One".

The advice to WP-codes not listed on the Repo? "Get listed."
=====

I recently started using "F2" ... an ancient artifact itself, now - I discover after the fact - rewritten using Underscore. Had I noted this relationship on first seeing the author's rewrite-description, I would have interpreted it as a Framework-like 'dependency', and thus passed on it. But I didn't catch the bit about _s, until I just now returned for deep-homework prep, before making an F2 Child.

Yet going full-circle, I find that the crypto-nomen Underscore(s?) was Toolbox-driven ('cept, TB was pragmatic). Hmm! And in the "announcement post" link, I see that the specific rationale-context that disqualified Toolbox, was NOT that it "was" or "is" broken, itself, but that turning it into, or updating it to support what the authors wanted, would break ... what was up until then, not broke? And still isn't ... yet it was dropped?

I would probably be all for promoting Son-of-Toolbox ... if it had a proper WordPress address. I will probably not be able to resist looking at it ... but it would have been a lot nicer, to see a blurb on the Toolbox page, promoting a new-and-improved version/project.