English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

The use of third-party packages is becoming increasingly popular and has ledto the emergence of large software package ecosystems with a maze ofinter-dependencies. Since the reliance on these ecosystems enables developersto reduce development effort and increase productivity, it has attracted theinterest of researchers: understanding the infrastructure and dynamics ofpackage ecosystems has given rise to approaches for better code reuse,automated updates, and the avoidance of vulnerabilities, to name a fewexamples. But the reality of these ecosystems also poses challenges to softwareengineering researchers, such as: How do we obtain the complete network ofdependencies along with the corresponding versioning information? What are theboundaries of these package ecosystems? How do we consistently detectdependencies that are declared but not used? How do we consistently identifydevelopers within a package ecosystem? How much of the ecosystem do we need tounderstand to analyse a single component? How well do our approaches generaliseacross different programming languages and package ecosystems? In this chapter,we review promises and perils of mining the rich data related to softwarepackage ecosystems available to software engineering researchers.

Promises and Perils of Mining Software Package Ecosystem Data