Curl’s Stenberg weighs two Rust rewrites against maintenance
Compare two Rust rewrites of curl, their compatibility claims and what packagers should check before replacing libcurl.
Curl creator Daniel Stenberg said on November 17 that two independent Rust reimplementations of curl and libcurl have appeared, but argued that keeping up with the original project’s fixes will matter more than rewriting its code. In his post, he said upstream had merged more than 300 commits, including over 200 bug fixes, during the newer rewrite’s development.
For distribution packagers and developers embedding libcurl, the projects offer alternatives to evaluate, not an upstream migration. Both claim compatibility with curl, but their build requirements, tested configurations and maintenance paths differ from the C implementation.
The first project, urlx, describes itself as a from-scratch implementation with a curl-like command-line tool, a Rust API and a C ABI layer. Its maintainers say 1,300 curl tests pass, while 92 are skipped and 25 are permanently excluded, including tests involving the libcurl C API. The README also lists HTTP/3 as untested and says TLS generally uses rustls, rather than OpenSSL.
The second, kov/curl, uses the curl name and says its Rust library provides libcurl.so.4 compatibility for existing programs without rebuilding. Its maintainer says the rewrite was produced with Claude Code under human direction and compared against C builds from the same source tree. The documented build needs a Rust toolchain, a C compiler and development packages for its C-library backends. Its listed platforms are Linux, macOS and Windows; NTLM is among the features it does not build.
Stenberg said he prefers continuous refactoring to rewrites in any language, while acknowledging that Rust has benefits in many cases. He estimated that 14 of curl’s 81 vulnerabilities confirmed so far in 2026 would most likely have been avoided with a memory-safe language. His further suggestion that the other 67 would remain is a judgment about a hypothetical implementation, not a measured result. His post expresses his position; it does not announce an upstream decision to replace curl with either project.
Packagers considering a substitution should check their required protocols, TLS backend and target platform, then run their applications’ compatibility tests against the candidate library. On Linux, the kov/curl README suggests checking which libcurl a program loads with:
ldd /usr/bin/curl | grep libcurl
Stenberg said he had not contacted either rewrite’s developers and did not know their long-term plans, including whether the projects would remain proofs of concept.
Comments ()