Security Vulnerabilities of Eclipse Application Programming Interfaces: An Empirical Analysis

dc.contributor.authorKawuma, Simon
dc.contributor.authorBamutura, David Sabiiti
dc.contributor.authorObbo, Aggrey
dc.contributor.authorKabarungi, Moreen
dc.contributor.authorKalungi, Dickson
dc.contributor.authorMabirizi, Vicent
dc.date.accessioned2026-11-19T07:47:45Z
dc.date.issued2026
dc.description.abstractThe Eclipse framework distinguishes between stable public APIs and less stable internal APIs; however, there is no formal assurance that these interfaces have been comprehensively evaluated for security vulnerabilities. Furthermore, previous studies revealed that many developers are unaware of most vulnerabilities. Applications that use security vulnerable APIs risk failing and are prone to malicious attacks if vulnerabilities are not fixed. Security vulnerability discovery is a difficult process and takes at least 3 years to discover and fix them. As a result, developers who depend on affected APIs are frequently compelled either to address these vulnerabilities independently or to discontinue their use. This study aims to identify interfaces within the Eclipse framework that are free from known security vulnerabilities and to recommend them for safer adoption by application developers. To achieve this objective, an empirical investigation was conducted using the SonarQube static analysis tool across 28 major Eclipse releases. The analysis focused on determining the presence and distribution of vulnerability-free inter faces. The study result Edina dataset comprising approximately 222K public APIs and 292K internal APIs that were found to be free of detected security issues. The findings reveal that, on average, about 91.4% of public APIs and 85.3% of internal APIs across the analyzed releases do not exhibit security vulnerabilities. Furthermore, the average time required to remediate identified vulnerabilities was estimated at 1,425 days. These results offer valuable guidance for both API providers and users by identifying more reliable interfaces and providing an indication of the effort required to resolve security issues. Additionally, the dataset of vulnerability-free interfaces has been made publicly accessible via GitHub to support the development of more secure software systems.
dc.identifier.citationKawuma, S., Bamutura, D. S., Obbo, A., Kabarungi, M., Dickson, K., & Mabirizi, V. (2026). Security Vulnerabilities of Eclipse Application Programming Interfaces: An Empirical Analysis. VAWKUM Transactions on Computer Sciences, 14(1), 96-109.
dc.identifier.urihttps://ir.must.ac.ug/handle/123456789/4786
dc.language.isoen_US
dc.publisherVAWKUM Transactions on Computer Sciences
dc.rightsAttribution-NonCommercial-NoDerivatives 4.0 Internationalen
dc.rights.urihttps://creativecommons.org/licenses/by-nc-nd/4.0/
dc.subjectEclipse
dc.subjectpublic APIs
dc.subjectinternal APIs
dc.subjectsecurity vulnerabilities
dc.subjectSoftware Quality
dc.subjectEvolution.
dc.titleSecurity Vulnerabilities of Eclipse Application Programming Interfaces: An Empirical Analysis
dc.typeArticle

Files

Original bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Security Vulnerabilities of Eclipse Application Programming Interfaces An Empirical Analysis.pdf
Size:
304.63 KB
Format:
Adobe Portable Document Format

License bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
license.txt
Size:
1.64 KB
Format:
Item-specific license agreed upon to submission
Description: