Skipper
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
A side-by-side editorial comparison of sociome and Verdaccio — release velocity, themes, recent moves, and the top alternatives to consider.
A six-year silence ends with the Area Deprivation Index rebuilt on the 2020 census.
sociome computes the Area Deprivation Index and related measures of social determinants of health from US census data. After patch releases in 2019 and 2020 the package went quiet, and version 3.0.0 in January 2026 returns with complete 2020 decennial census support, expanded ZCTA coverage, and helper objects that tell users up front which dataset, year and geography combinations the census API will actually serve.
Verdaccio's 7.0 line is subtraction — forks dropped, toolchain swapped, tags mostly empty
The next-7 prerelease line is short and almost entirely maintenance. Its one substantive release adopted @verdaccio/server and deleted the local api, web, and storage forks, leaving a thin Storage wrapper behind only to keep callback-based storage plugins working. Everything since has been dependency retargeting, a lint and format toolchain swap, and a tag whose body reads 'chore: trigger release'.
sociome computes the Area Deprivation Index and related measures of social determinants of health from US census data. After patch releases in 2019 and 2020 the package went quiet, and version 3.0.0 in January 2026 returns with complete 2020 decennial census support, expanded ZCTA coverage, and helper objects that tell users up front which dataset, year and geography combinations the census API will actually serve.
The package's usefulness is tied to a data generation, and this release moves it a full census cycle forward. The other changes point the same way: better input checking so failures surface before an API call rather than after, a documented availability matrix, and removal of the seed argument from the three main entry points. That last one is a breaking change and suggests the underlying computation stopped being stochastic in the way it was.
With 2020 support landed, the pressure shifts to annual American Community Survey vintages rather than decennial ones. Expect maintenance around that rather than another overhaul.
The next-7 prerelease line is short and almost entirely maintenance. Its one substantive release adopted @verdaccio/server and deleted the local api, web, and storage forks, leaving a thin Storage wrapper behind only to keep callback-based storage plugins working. Everything since has been dependency retargeting, a lint and format toolchain swap, and a tag whose body reads 'chore: trigger release'.
This is consolidation ahead of a major: the project is collapsing code it had been carrying in-tree back onto shared packages and standardising tooling around oxlint and oxfmt. The remaining compatibility shim is the visible unfinished business — it exists purely for legacy plugins, and it is the last thing standing between this line and a clean server dependency.
Removing the legacy storage wrapper is the decision this line is heading toward, and it breaks callback-based storage plugins when it lands, so expect it to arrive with the 7.0.0 final rather than in another next tag. Until then the prerelease stream will keep producing tags with no user-visible content.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either sociome or Verdaccio.
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Kinsta is moving MyKinsta's controls into its API, one surface per month
Observability lands on OpenTelemetry semconv in the LTS train
Canvas agents gain memory, and onboarding moves into the editor
Security and governance controls catch up to the Copilot build-out
See all sociome alternatives → · See all Verdaccio alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Verdaccio is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Verdaccio is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top sociome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "sociome alternatives" section above for the current picks, or visit /alternatives/sociome for the full list with editorial commentary on each.
Top Verdaccio alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Verdaccio alternatives" section above for the current picks, or visit /alternatives/verdaccio for the full list with editorial commentary on each.