Protectedcategory'' is everything; the rest are the keys of Packagist::CATEGORIES.
ProtectedcheckingProtectedcompactOne formatter for every card's download count; the locale does not change while the page is open.
ProtectedcoreProtectederrorProtectedinstalledProtectedlastThe query whose results are on screen, so a keystroke can tell if anything changed.
ProtectedloadingProtectedminimumProtectedmoreProtectedpageProtectedqueryProtectedresultsProtectedsearchedProtectedsearchingProtectedseqProtectedshownThe query and category the results on screen belong to, which "Show more" pages through. Not the search box: what is typed there may not have been searched yet, and its second page appended under the first page of something else.
ProtectedtypingThe pending debounce, so a new keystroke replaces it rather than adding to it.
ProtectedverdictsPackagist records a replacement package when the author names one, and that is the single most useful thing to say about an abandoned extension.
Whether the forum's minimum stability lets Composer install this release.
Four states, and "we don't know yet" is one of them. Collapsing unknown into "no" hides working extensions; collapsing it into "yes" offers ones that cannot install. Either way somebody stops believing the badge.
Optionalv: VerdictA keystroke, considered.
The rule lives in searchPolicy so it can be tested; this is only the timer.
A download count, abbreviated the way the forum's locale does it: 220K, 1.5M; 220 k, 1,5 M in French.
The next page, appended.
Appended rather than replacing, because browsing is a scroll and losing what you already looked at to see more of it is the wrong trade. Each page costs its own compatibility pass, which is why they are fetched a page at a time rather than all 2306 at once.
Finding something to install.
The one thing this does that a bare Packagist search does not: it says whether a result works with the Flarum you actually have, BEFORE you press anything — not at install time, after the resolve, after the wait, and in the form of a constraint error rather than a sentence.
Verdicts arrive in a second request, so results appear immediately and the badges fill in. Waiting on a dozen round trips before showing anything would be the slower, worse version of the same screen.