The study identifies 13 categories of code smells in build scripts, detects 10,895 occurrences across 5882 scripts from 4877 repositories, and finds common patterns like insecure URLs in Maven and hardcoded paths in Gradle and CMake.
Title resolution pending
2 Pith papers cite this work. Polarity classification is still indexing.
2
Pith papers citing it
fields
cs.SE 2representative citing papers
Empirical analysis of 233 framework code samples reveals they are typically small, frequently updated for compatibility, and mostly used without modification after forking.
citing papers explorer
-
Your Build Scripts Stink: The State of Code Smells in Build Scripts
The study identifies 13 categories of code smells in build scripts, detects 10,895 occurrences across 5882 scripts from 4877 repositories, and finds common patterns like insecure URLs in Maven and hardcoded paths in Gradle and CMake.
-
Framework Code Samples: How Are They Maintained and Used by Developers?
Empirical analysis of 233 framework code samples reveals they are typically small, frequently updated for compatibility, and mostly used without modification after forking.