MétaCan
Menu
← Back to cohort
Record W7160228089

Bugspyter : detecting code bugs in Jupyter Notebooks using LLMs

2025· other· en· W7160228089 on OpenAlexaff
Oluwadabira Omotoso

Bibliographic record

VenuecIRcle (University of British Columbia) · 2025
Typeother
Languageen
Field
Topic
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsRoot causeSoftware bugDebuggingSecurity bugSoftwareReliability (semiconductor)Code (set theory)Root (linguistics)
DOInot available

Abstract

fetched live from OpenAlex

Computational notebooks are increasingly used in the fields of data science, computer science, classrooms, the software industry, and various fields. However, users often encounter errors, bugs, and vulnerabilities related to modularized code, unexecuted cells, and outdated library versions. This paper presents a tool, Bugspyter, designed to detect and repair code bugs in Jupyter Notebooks using LLMs. We develop an agent-based model to test the performance of the LLM in identifying the bug types and the root causes of these bugs in the notebooks, along with enhancing the model with static analysis results. Our results show that Bugspyter can identify buggy notebooks and has a high accuracy for identifying implementation bug types in notebooks. Additionally, it can identify coding errors as the root cause of bugs in a notebook but fails to perform well in other root causes of bugs. Furthermore, we see an improvement in the performance of LLMs when identifying bugs in executed notebooks but no change in performance with the inclusion of static analysis results. This study contributes valuable insights into enhancing the reliability of computational notebooks, as it helps to reduce the need for many manual evaluations to fix these issues.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.025
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.018
Threshold uncertainty score0.035

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.025
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0030.001
Science and technology studies0.0010.001
Scholarly communication0.0020.004
Open science0.0030.003
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0050.003

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.013
GPT teacher head0.198
Teacher spread0.185 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2025
Admission routes1
Has abstractyes

Explore more

Same venuecIRcle (University of British Columbia)→French-language works237,207→