Towards Using Package Centrality Trend to Identify Packages in Decline · HackerPapers discussionshttps://hackerpaper.kaipfister.de/p/2107.10168/Collected HN comments and submissions linking this paper.enMon, 02 Nov 2026 11:16:22 GMTTowards Using Package Centrality Trend to Identify Packages in Decline — mentioned by suhaibmujahidhttps://news.ycombinator.com/item?id=28248419urn:hackerpapers:mention:2107.10168:28248419Fri, 20 Aug 2021 17:01:59 GMT<p>The npm registry has more than 1.7 million JavaScript packages. While the community shifts to adapt to new packages (usually better ones). New packages are not necessarily better. But, if the community is moving toward using a specific modern package, probably it is for a reason. The question is: How to measure the community shift? Can downloads catch that? Actually, downloads are not quite good at that. We created a Chrome extension called &quot;Centrality Checker&quot; to help you not to be left behind. Our tool prototype uses the package centrality over time to identify community interest. More…</p><p><a href="https://hackerpaper.kaipfister.de/p/2107.10168/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.SE