Developers build on Application Programming Interfaces (APIs) to reuse existing functionalities of code libraries. Despite the benefits of reusing established libraries (e.g., time savings, high quality), developers may diverge from the API's intended usage; potentially causing bugs or, more specifically, API misuses. Recent research focuses on developing techniques to automatically detect API misuses, but many suffer from a high false-positive rate. In this article, we improve on this situation by proposing ChaRLI (Change RuLe Inference), a technique for automatically inferring change rules from developers' fixes of API misuses based on API Usage Graphs (AUGs). By subsequently applying graph-distance algorithms, we use change rules to disc...
Analyzing the Change-Proneness of APIs and web APIs APIs and web APIs are used to expose existing bu...
Software components expose Application Programming Interfaces (APIs) as a means to access their func...
Description: Artifact Package for the paper Dealing with Variability in API Misuse Specification, ac...
Today's software industry relies heavily on the reuse of existing software libraries. Such libraries...
This repository contains the source code as well as all evaluation scripts and dataset links to repl...
API misuses are prevalent and extremely harmful. Despite various techniques have been proposed for A...
Over the last few years, researchers proposed a multitude of automated bug-detection approaches that...
Software application programming interfaces (APIs) are a ubiquitous part of Software Engineering. Th...
Application Programming Interfaces (APIs) typically come with (implicit) usage constraints. The viol...
International audienceA significant percentage of warnings reported by tools to detect coding standa...
APIs are the primary mechanism for developers to gain access to externally defined services and tool...
Application Programming Interfaces (APIs) in cryptography typically impose concealed usage con...
peer reviewedAndroid app developers recurrently use crypto-APIs to provide data security to app user...
Software projects make use of libraries extensively. Libraries have intended API surfaces—sets of ex...
Library developers are often unaware of how their library is used exactly in practice. When a librar...
Analyzing the Change-Proneness of APIs and web APIs APIs and web APIs are used to expose existing bu...
Software components expose Application Programming Interfaces (APIs) as a means to access their func...
Description: Artifact Package for the paper Dealing with Variability in API Misuse Specification, ac...
Today's software industry relies heavily on the reuse of existing software libraries. Such libraries...
This repository contains the source code as well as all evaluation scripts and dataset links to repl...
API misuses are prevalent and extremely harmful. Despite various techniques have been proposed for A...
Over the last few years, researchers proposed a multitude of automated bug-detection approaches that...
Software application programming interfaces (APIs) are a ubiquitous part of Software Engineering. Th...
Application Programming Interfaces (APIs) typically come with (implicit) usage constraints. The viol...
International audienceA significant percentage of warnings reported by tools to detect coding standa...
APIs are the primary mechanism for developers to gain access to externally defined services and tool...
Application Programming Interfaces (APIs) in cryptography typically impose concealed usage con...
peer reviewedAndroid app developers recurrently use crypto-APIs to provide data security to app user...
Software projects make use of libraries extensively. Libraries have intended API surfaces—sets of ex...
Library developers are often unaware of how their library is used exactly in practice. When a librar...
Analyzing the Change-Proneness of APIs and web APIs APIs and web APIs are used to expose existing bu...
Software components expose Application Programming Interfaces (APIs) as a means to access their func...
Description: Artifact Package for the paper Dealing with Variability in API Misuse Specification, ac...