Studies LH002
When something changes in a small software neighbourhood, where does the change appear next?
The answer so far. In this neighbourhood the change travelled, and the public record shows where it went but not why. Within the window, four of the nine dependents' repositories came to hold the library's new release, mcp 1.27.0. The earliest record of it is R04's first GitHub commit, 2.1 days after publication, which already held it; the first move visible as a change came 6.2 days after publication. In one case the release went a further step: a dependent's own release, published 22 minutes after its update, pinned it for everyone who installs that dependent (observation and derived measurement, git and Open Source Insights). All four moves are explained by ordinary maintenance: a maintainer's standing habit of pinning each new release, this time 22 minutes before the project's own release, a bulk lockfile refresh, the pinning of another package's dependencies, and a first adoption. No identified bot made any of them, and no maintainer identity is shared with the library (derived measurement; interpretation for "explained").
Study, version 0.2, 26 September 2026 studies/LH002/LH002.md
- LH002 study brief studies/LH002/brief.md
- LH002 cohort studies/LH002/cohort.md
From studies/LH002/ in the repository, last changed 9 November 2026.