Beyond download counts
Package registries are wonderful for discovery and terrible as a sole engagement score. A CI cache, a tutorial clone, and a production service can look identical in the download graph. Maintainers who celebrate the spike often miss the quiet exodus two majors later.
A ladder, not a vanity spike
We teach a simple ladder in Library Adoption Signals: package resolved → first public symbol executed without error → repeated use across seven days → use across a major version boundary. Each rung answers a different question. Collapsing them into “active users” hides whether your pain is documentation, API shape, or upgrade trauma.
When downloads still matter
They matter for supply-chain risk and for rough awareness. Treat them as weather, not climate. Pair them with qualitative notes from issues and Discord — numbers without narrative become slide decoration.
Start smaller than you think
Instrumenting twenty events to “catch up” usually creates renaming debt. Pick the next decision your team must make — deprecate an API, rewrite a guide, delay a release — and measure only what informs that choice. Application analytics for developer library engagement earns trust when it stays humble.