esx_lib surges; a handful of steady climbers shape the week

This week’s adoption picture is narrow and concentrated. Total distinct resource names observed across servers increased to 1,691,624 (previous week 1,670,730), but almost all attention sits with a handful of resources that either inched forward or moved decisively. The single clearest story is esx_lib’s continuous climb: it added 702 servers and recorded growth every measured day. Outside that movement there are small, steady increases among established libraries and tools — oxmysql, pma-voice, ox_lib and ox_target each added a few hundred servers spread over the week — but none match the shape of esx_lib’s week-long rise. The sustained-adoption list contains three items: esx_lib, esx_rpchat and esx_ambulancejob, and they are the only resources that satisfy our rule of growing on five or more measured days. A single resource, informational, shows a clear fall: it declined by 194 servers and did not grow on any measured day. New resource names continue to appear; most are small or private by reach, but a handful exceeded the threshold we treat as noteworthy in their first seven days. In short: one strong sustained mover, a set of incremental gains among the usual suspects, and a tidy, visible drop worth watching.

Sustained gains are the most informative signal in our weekly window because they imply distributed adoption rather than a single bundle pushing a resource into many servers at once. esx_lib is the dominant narrative this week. esx_lib grew on 6/6 days and finished on 1,559 servers (prev week 857), a net +702. Its daily sequence — 1301→1386→1481→1558→1633→1728→1824 — shows repeated, multi-day additions rather than a single spike, which is exactly the shape we consider evidence of organic spread across multiple servers. Two ESX-facing scripts joined it on the sustained list. esx_rpchat grew on 5/6 days and ended at 4,297 servers (prev week 4,152), a +145 net change; its daily numbers (4239→4257→4315→4318→4285→4326→4337) show steady small steps with one minor dip mid-week. esx_ambulancejob also grew on 5/6 days and added +142 to reach 4,139 servers (prev week 3,997), with daily readings 4108→4128→4153→4157→4132→4146→4152. Those two are familiar ESX modules and their week-long patterns are the kind we treat as slow, networked adoption: modest per-day increases that accumulate into meaningful reach over time. A second tier of movers added a few hundred servers but with mixed daily shapes. oxmysql (+424 to 29,825) and pma-voice (+393 to 27,643) both recorded gains on four measured days; their daily sequences include small up-and-down jitter, suggesting a mix of steady installs and normal churn. ox_lib (+334), bob74_ipl (+411) and ox_target (+210) added similar modest totals but did not show the same every-day climb. (+224), (+209) and (+190) are further examples: real growth, but interrupted by drops on some days. For developers, the contrast matters: esx_lib’s uninterrupted six-day run looks like a resource being recommended or required in a growing number of servers; the others are useful and increasing, but their week shows the usual market friction — installs, removals and restarts — that produces a less clean signal.

The cleanest decline this week belongs to informational. informational grew on 0/6 days and fell from 2,895 to 2,702 servers, a loss of 194. Its daily run (2803→2754→2732→2700→2655→2643→2625) is a straight decline with no recovery day, which is exactly the pattern that points to a single cause spreading across many servers — for example a breakage, deprecation or an active removal — rather than normal jitter. The magnitude is not enormous in absolute terms, but the shape matters: dropping every measured day with no gains is not normal churn. No other resource in the top movers list shows a comparable total disappearance; most losses elsewhere are fractional or appear as single-day dips inside otherwise mixed sequences. That makes informational the only resource this week that qualifies as a clear, sustained decline. Watch it next week: if the fall continues the resource may be failing or being replaced in a lot of servers, and if it stabilises the move may simply have been a concentrated cleanup across a cluster of servers.

The week produced a handful of brand-new resource names that reached non-trivial server counts in their first seven days. onx-evp-b-audio is the largest newcomer, first seen 2026-07-30, and it reached 104 servers in its debut week. Two other new names cleared the 60-server mark: gmz_r2514dw (first seen 2026-07-28) reached 71 servers, and Wheelchair2000 (first seen 2026-07-30) reached 62. A second group of smaller new entries includes rpemotes-reborn-2.1.3 (48 servers), spectrerenegade (37), mt_mrpd (32) and several others in the high-twenties. Most new resource names are the work of a single server’s private code and never travel beyond one installation; when a name reaches dozens of servers inside its first week it is worth noting. These newcomers are not yet large enough to change the platform’s dependency map, but their first-week reach merits a follow-up: if any of them adds consistent daily growth next week they will graduate into the rising category.

What to watch next week is straightforward. esx_lib is the primary candidate for continued attention: it added +702 across six growth days and its every-day climb is the exact pattern that signals genuine spread rather than a one-off bundle. Developers that build ESX integrations should verify compatibility and consider whether their modules depend on esx_lib or duplicate its functionality. The ESX chat and ambulance modules (esx_rpchat and esx_ambulancejob) are secondary but meaningful steady movers; their slow, multi-day increases suggest they remain actively used and worth supporting. Monitor informational closely: a straight, seven-day decline likely indicates a breaking change, deprecation, or coordinated removal and could affect any module that depends on it. For server owners, the newcomers that exceeded 60 servers (onx-evp-b-audio, gmz_r2514dw, Wheelchair2000) deserve a closer look for stability and security before broad deployment; they are interesting early signals but not yet proven. Finally, expect more of the same: core libs will continue to grow slowly, not explode, and a true change in the dependency landscape requires sustained multi-day adoption, which is still the decisive signal in our weekly window.