Adoption stalls; no sustained climbers this week

This week’s data is simple and, for developers hoping for breakout growth, disappointing: the scanner saw 1,543,298 distinct resource names (previous week 1,557,141) with 93% overall coverage. That drop in the universe of visible resources is the clearest headline — more resources disappeared from servers than appeared. Crucially, none of the tracked scripts satisfied our sustained-adoption rule (growth on 5 or more of the six measurement transitions). That rule is deliberately strict; a week’s total alone hides whether a script is genuinely spreading or merely piggybacking on a single large server update. With no names meeting the 5+ days test, the week reads as jitter and reconfiguration rather than organic spread. The scanner did record notable losses: the resource named core lost 249 servers (−20.3%) and several widely deployed qb-* and utility resources trimmed roughly 100–140 servers each. Those declines mostly show as multi-day falls with only two growth days in the six transitions listed — the shape is consistent with widespread removals or configuration changes rather than a single one-off outage. On the other side, a small set of freshly seen phone-* scripts and a few other newcomer names reached dozens of servers in their first week; that’s the only real bright spot, but it is still early adoption rather than demonstrated momentum. With coverage at 93%, week-to-week comparisons are valid but caution is warranted: missing scans can mute small gains or losses, and single-server updates can still create visible but transient spikes.

Loss, not growth, dominated this week’s movement. The single largest measurable fall is core: it fell 249 servers to 978 (−20.3%). Its daily line is telling — 975→927→908→940→1054→1042→1042 — an early-week drop followed by a midweek rebound that did not fully restore prior counts. That shape is consistent with a broad removal or configuration change across many servers, with some later restorations or re-adds. We do not know the cause from scans alone; possible explanations include a breaking change, a mass migration to an alternative, or a coordinated removal in server packs. Several commonly used resources also posted steady net losses in the 100–140 server range and, like core, “grew” on only two of the six transitions. Examples: oxmysql is listed at 29,862 servers (prev week 30,001), −138 (daily: 30015→29942→29917→29482→30148→29731→29919), qb-minigames is down 131 to 5,636, qb-jewelery down 129 to 3,894, interact-sound down 123 to 11,295, and a set of qb-* gameplay modules (qb-newsjob, qb-houserobbery, qb-weathersync, qb-storerobbery, qb-spawn) each lost roughly 118–119 servers. Those declines share a common signature: slow erosion across the week with only brief upticks, not concentrated single-day churn. That pattern suggests either ongoing pruning by server operators (removing underused resources), the slow rollout of alternative scripts, or fallout from a shared dependency change. From an operational standpoint, any project depending on core or the affected qb modules should treat this week as a warning sign: something in the ecosystem produced removals across many servers, and the partial midweek recoveries show the story is still unsettled.

This week produced a compact, coherent set of new names — most notable are phone- prefixed resources. phone-vehicles was first seen 2026-05-18 and reached 66 servers in its first week. phone-discord (first seen 2026-05-19) reached 61 servers. phone-lottery and phone-vendingmachine appeared as well, at 38 and 20 servers respectively, indicating multiple phone-related packages are being deployed in parallel. Those four are the clearest newcomer cluster and are worth watching because they can bootstrap each other: phone frameworks commonly attract complementary modules that spread together when a host adopts the ecosystem. Beyond the phone cluster, rpemotes-reborn-2.1.1 (first seen 2026-05-21) reached 33 servers and H79-rc_alarm hit 47 servers after a 2026-05-22 first sighting. A handful of single-package names — Abuabdullaziz_shelby_car8 (21), modern_chat_theme (19), sis_yellow_jack (19), and u4i-torment (18) — also appeared. Most of these counts are modest, but they matter: new names that reach dozens of servers in week one have cleared the “single private server” threshold and entered the field of things other server owners might consider. None of the newcomers yet show the daily stair-step pattern that would mark them as sustained spreads; for now they are early entrants to keep an eye on.

What to do next week: first, assume movement is slow and verify any dependency changes rather than reacting to single-week noise. The absence of sustained climbers means there is no clear ‘must adopt’ script emerging this week. If you ship a resource, focus on making it easy to adopt incrementally — small, dependable installs across many servers are what produce 5+ day growth. For server owners: if you rely on core or the qb modules that shed servers, run quick compatibility checks; a partial midweek recovery in core suggests whatever caused the drop may be fixable or reversible, but you should not assume it is resolved. For integrators and pack maintainers: the phone-* cluster is worth a short evaluation pass. phone-vehicles reached 66 servers in its first week and phone-discord 61; that level of initial uptake is the sort of signal that justifies a short compatibility test on staging. Finally, keep an eye on scan coverage next week — we ran at 93% this week, and lower coverage increases noise. The actionable lesson for developers is unchanged: steady, visible adoption looks like small, repeated daily gains. This week produced none of them, so the most valuable activity is defensive — harden compatibility, reduce friction for incremental installs, and watch whether any of this week’s newcomers convert initial interest into multi-day growth.