Papers for

software repository managers

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

CodeGraph builds a large knowledge graph linking source code to real-world concepts

CodeGraph: Open-Taxonomy Knowledge Graph for Source Code with Wikidata Grounding

Abstract: Public software repositories, like GitHub and Software Heritage Archive, store billions of files, yet extracting their implicit engineering knowledge ---i.e., the algorithms they implement, the paradigms they follow, the patterns they instantiate, and the application domains they serve--- remains challenging, as current tools are constrained to syntactic and token-level analysis. We present a pipeline for building an open-taxonomy semantic annotation of source code using a code-specialised Large Language Model. The extracted entities are grounded in Wikidata through a three-stage linking procedure: a deterministic SPARQL stage handles unambiguous entities, a Deep Research Agent resolves the residual long tail, and a hierarchy-rollup stage imports the parent-of closure of each resolved Wikidata identifier. The resulting annotations are materialised as a source-code-specific open-taxonomy knowledge graph. We further introduce a calibrated quality-assurance protocol that quantifies annotation precision by combining a small human gold set with an LLM-as-a-judge filter. We applied our pipeline to the 167 million files of the Stack-Edu corpus, creating the first known large-scale open-taxonomy knowledge graph for source code. Our graph, named CodeGraph, contains approximately 158 million nodes, which include around 145 million files, about 63,000 extracted concept entities (such as algorithms, paradigms, design patterns, and application domains), and roughly 19,800 grounded Wikidata entities. Furthermore, CodeGraph features approximately 1 billion typed edges that connect files to their respective concepts, link these concepts to their grounded Wikidata identifiers, and relate them to their parent categories, covering 14 programming languages.

Thu 24 SeptSoftware EngineeringComputation and LanguageInformation Retrieval
The gist
Source code stored in huge public collections is hard to understand because it’s mostly analyzed by looking at syntax or text alone. The authors created a new tool that uses a large AI language model specialized for coding to identify meaningful programming concepts within code files. They match these concepts to real-world knowledge in Wikidata, organizing everything into a big graph that connects code files with programming ideas and categories. This graph covers many programming languages and could help people explore and understand code more deeply.
Open → 2609.29474v1

GitHub projects keep local coding styles despite AI influence

Converging Naming Styles, Persistent Network Locality: GitHub in the LLM Era

Abstract: Social conventions often emerge through repeated interactions within social networks, allowing shared practices to coexist with variation across groups. Large language models (LLMs) introduce a potentially different coordination structure: a small number of widely used models can expose socially distant users to similar patterns and suggestions. Whether broad convergence under such shared technological influences eliminates network-local variation remains unclear. We examine this question in software development, where identifier naming styles provide observable conventions and LLM-based tools have rapidly diffused. Using public GitHub repositories created between 2015 and September 2025 across six programming languages, we characterize naming styles with 27 features and examine their association with detected LLM-related commits, their diversity across repository creation cohorts, and their relationship to owner proximity in a large-scale collaboration network. Repositories with detected LLM-related commits tend to use longer identifiers and, in several languages, make greater use of naming patterns already prevalent within the language. We also observe lower naming-style diversity in recent creation cohorts, with marked declines appearing around 2023-2024 in several languages, although their timing and trajectories differ. At the same time, network locality persists: in five of the six languages, repositories whose owners are closer in the collaboration network remain more similar in naming style even among recent, more homogeneous cohorts. These findings show that aggregate convergence and network-local variation can coexist, highlighting the need to examine not only how much cultural variation remains, but also how that variation continues to be structured by human social relationships in the era of widely shared AI systems.

Thu 17 SeptSocial and Information Networks
The gist
This paper looks at how programmers name things in their code on GitHub, especially now that AI tools help them. Even though AI suggests similar naming styles to many users everywhere, smaller groups of developers still keep their own local naming habits. The authors found that recent projects use longer names and less variety overall, but people working closer together in GitHub’s network still have more similar styles. This means AI influences naming but doesn’t erase local coding cultures.
Open → 2609.19864v1

HLSFactory-Agent automates extraction of hardware designs from code

HLSFactory-Agent: Large-Scale Agentic HLS Dataset Construction from Academic and Open-Source Projects

Abstract: Building large, diverse datasets of high-level synthesis (HLS) designs beyond common community benchmarks remains an open challenge. This challenge is made urgent by the rise of deep learning and LLMs for hardware design, which demand such datasets to train QoR models and benchmark LLMs on HLS tasks. Despite ongoing efforts to broaden sources, dataset curation still depends on manual work: locating HLS designs across academic publications and open source, then extracting standalone designs from larger codebases. The process is error-prone and demands expert knowledge, iterative testing, and substantial per-repository engineering. To address this, we present HLSFactory-Agent, an LLM agent that automates large-scale HLS dataset curation by extracting standalone designs from larger codebases. HLSFactory-Agent runs the open-source Pi agent framework inside Docker containers to build and evaluate each extracted design. This turnkey automation allows users to pass a GitHub link or code directory to HLSFactory-Agent and receive a folder of extracted HLS designs ready to be integrated into the HLSFactory dataset framework. Additionally, we provide open-source scripts to scrape and index papers from computer architecture, EDA, and FPGA conferences that possibly implement or use HLS designs, allowing for faster human discovery and curation of HLS designs for HLSFactory-Agent. We report initial results from running HLSFactory-Agent across a small subset of our indexed repositories, demonstrating successful extraction of synthesizable designs from structured codebases. We open source HLSFactory-Agent and indexing scripts at https://github.com/sharc-lab/hlsfactory-agent.

Tue 8 SeptHardware ArchitectureSoftware Engineering
The gist
It is hard and time-consuming for experts to find and prepare collections of hardware design projects from academic papers and open-source sites. The authors created HLSFactory-Agent, a software helper that uses AI to automatically pick out standalone hardware designs from big code collections. This tool can test and build each design to make sure it works, saving lots of manual effort. They also made scripts to search and organize papers to find projects faster. Their results show it can successfully extract usable hardware modules from some example repositories.
Open → 2609.09519v1