Preprint · 2026 · Open access
API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors
SSRN Electronic Journal · Published 1 January 2026 · DOI 10.2139/ssrn.6143771
In brief
“API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors” is a 2026 preprint by Ivan I. Petrov and 2 co-authors, published in SSRN Electronic Journal. OpenAlex counts 0 citations as of 19 November 2026. It is open access: the full text is free to read at SSRN Electronic Journal.
- Citations
- 0
- Authors
- 3
Cite this paper
Formatted from the catalogue record. Check names, capitals and page numbers against the paper before you submit.
APA 7
Petrov, I. I., Kuznetsova, E., & Sokolova, M. (2026). API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors. SSRN Electronic Journal. https://doi.org/10.2139/ssrn.6143771
MLA 9
Petrov, Ivan I., et al. “API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors.” SSRN Electronic Journal, 2026. https://doi.org/10.2139/ssrn.6143771.
Chicago
Petrov, Ivan I., Elena Kuznetsova, and Maria Sokolova. 2026. “API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors.” SSRN Electronic Journal. https://doi.org/10.2139/ssrn.6143771.
Harvard
Petrov, I. I., Kuznetsova, E. and Sokolova, M. (2026) ‘API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors’, SSRN Electronic Journal. doi:10.2139/ssrn.6143771.
IEEE
I. I. Petrov, E. Kuznetsova, and M. Sokolova, “API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors,” SSRN Electronic Journal, 2026, doi: 10.2139/ssrn.6143771.
BibTeX
@misc{petrov2026misuse,
title = {{API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors}},
author = {Petrov, Ivan I. and Kuznetsova, Elena and Sokolova, Maria},
howpublished = {SSRN Electronic Journal},
year = {2026},
doi = {10.2139/ssrn.6143771},
url = {https://doi.org/10.2139/ssrn.6143771}
}
Download for a reference manager: BibTeX (.bib) · RIS for Zotero, Mendeley and EndNote (.ris)
Topic and keywords
Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- API misuse detection
- LLM-generated code
- code security
- error handling
- software vulnerability detection
Work with this paper
Most-cited papers in Computer Science
- ImageNet classification with deep convolutional neural networksAlex Krizhevsky, Ilya Sutskever, Geoffrey E. Hinton · Communications of the ACM · 2017 · 114,726 citations
- Long Short-Term MemorySepp Hochreiter, Jürgen Schmidhuber · Neural Computation · 1997 · 109,097 citations
- A Mathematical Theory of CommunicationClaude E. Shannon · Bell System Technical Journal · 1948 · 91,736 citations
- Deep learningYann LeCun, Yoshua Bengio, Geoffrey E. Hinton · Nature · 2015 · 90,226 citations
- Faster R-CNN: Towards Real-Time Object Detection with Region Proposal NetworksShaoqing Ren, Kaiming He, Ross Girshick and 1 more · IEEE Transactions on Pattern Analysis and Machine Intelligence · 2016 · 74,143 citations
Questions about this paper
How do I cite this paper in APA style?
Petrov, I. I., Kuznetsova, E., & Sokolova, M. (2026). API Misuse Detection in LLM-Generated Code Using Transformer-Based Context Modeling Authors. SSRN Electronic Journal. https://doi.org/10.2139/ssrn.6143771
How many times has this paper been cited?
0 times, according to OpenAlex on 19 November 2026. Google Scholar and Scopus count different sets of sources, so their numbers differ.
Is this paper free to read?
Yes. It is open access at SSRN Electronic Journal: sign in and open the full text from this page.
Who wrote this paper?
Ivan I. Petrov, Elena Kuznetsova, Maria Sokolova.
What is the DOI of this paper?
10.2139/ssrn.6143771, permanently at https://doi.org/10.2139/ssrn.6143771. Sign in and open it from this page.
Bibliographic data from OpenAlex (CC0), last checked 19 November 2026. ResearchGuru does not host this paper; once you are signed in, the links open it at the publisher or the repository that does.