Most research on third-party dependencies in software projects concentrates on version updates. A new arXiv preprint takes a different angle, looking at how developers reclassify dependencies over time. The authors note that dependency declarations must be maintained as projects evolve, yet this reclassification process has received far less attention than version bumps.

The study is longitudinal, meaning it follows JavaScript projects across multiple points in time. By focusing on reclassifications—changes in how dependencies are declared or categorized—the work aims to reveal patterns that version-centric studies miss. The abstract does not detail specific findings, but it clearly frames a research gap.

This is the only source provided, so there are no contrasting results to compare. The paper is available as arXiv:2604.08747v5.