Skip to content
aiqbench takeMachine Learning

aiqbench analysis

This study empirically validates the viability of LLM-assisted development for creating zero-dependency Python libraries, demonstrating that stdlib-only implementations often match or significantly outperform third-party alternatives in footprint and import speed. While performance parity holds for most logic, the research highlights a critical limitation where C-extension-backed tasks like image processing still require external dependencies. The findings provide concrete evidence-based tradeoffs for engineers balancing supply-chain security against computational efficiency in AI application stacks.
Source coveringarXiv
What this isA model's reading of the article and related coverage, written for aiqbench. Not the publisher's words.

Stdlib or Third-Party? Empirical Performance and Correctness of LLM-Assisted Zero-Dependency Python Libraries

arXiv2 min read

arXiv:2605.21405v2 Announce Type: replace-cross Abstract: Third-party Python libraries introduce dependency-management overhead, supply-chain risk, and deployment friction. We study when eliminating a dependency preserves enough correctness and performance to justify the gains in footprint, deployability, and trust surface. Our testbed is zerodep, 44 single-file, stdlib-only Python modules spanning 12 categories, each benchmarked against its reference library. Three performance regimes emerge. Stdlib-only implementations achieve parity (within 2x) in the majority of cases; many outperform their references by 5x-115x where architectural overhead dominates; and a clear cliff appears for C-extension-backed computation (image processing, binary serialization, low-level crypto), confirmed by PyPy JIT and profiling experiments. Beyond speed, stdlib modules reduce installed footprint by orders of magnitude (median 31 KB vs. 700 KB), import 2.2x faster, and eliminate 88 transitive dependencies maintained by 128 distinct PyPI accounts. Analysis of the LLM-assisted development process across all 44 modules shows that specification completeness, not model capability, is a strong predictor of generation success, and that contract-linked review reduces review volume by 5x while eliminating compatibility regressions. Together, these results turn dependency elimination from an anecdotal coding style into an evidence-based engineering tradeoff.

Title:Stdlib or Third-Party? Empirical Performance and Correctness of LLM-Assisted Zero-Dependency Python Libraries

Abstract:Third-party Python libraries introduce dependency-management overhead, supply-chain risk, and deployment friction. We study when eliminating a dependency preserves enough correctness and performance to justify the gains in footprint, deployability, and trust surface. Our testbed is zerodep, 44 single-file, stdlib-only Python modules spanning 12 categories, each benchmarked against its reference library. Three performance regimes emerge. Stdlib-only implementations achieve parity (within 2x) in the majority of cases; many outperform their references by 5x-115x where architectural overhead dominates; and a clear cliff appears for C-extension-backed computation (image processing, binary serialization, low-level crypto), confirmed by PyPy JIT and profiling experiments. Beyond speed, stdlib modules reduce installed footprint by orders of magnitude (median 31 KB vs. 700 KB), import 2.2x faster, and eliminate 88 transitive dependencies maintained by 128 distinct PyPI accounts. Analysis of the LLM-assisted development process across all 44 modules shows that specification completeness, not model capability, is a strong predictor of generation success, and that contract-linked review reduces review volume by 5x while eliminating compatibility regressions. Together, these results turn dependency elimination from an anecdotal coding style into an evidence-based engineering tradeoff.

Software Engineering (cs.SE); Artificial Intelligence (cs.AI); Programming Languages (cs.PL)

arXiv:2605.21405 [cs.SE]

(or arXiv:2605.21405v2 [cs.SE] for this version)

https://doi.org/10.48550/arXiv.2605.21405 Focus to learn more arXiv-issued DOI via DataCite

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

Full text under the publisher's open licence · 290 words

Related coverage