Chardet 7.0.0 Lgpl Obligation Dispute And Evidentiary Status

Issue 86 Edition 2026-03-27 4 min read

Not accepted General

Sources: 1 • Confidence: Medium • Updated: 2026-04-13 03:54

Key takeaways

Richard Fontana states that he currently sees no basis for concluding that chardet 7.0.0 is required to be released under the LGPL.
Richard Fontana states that no one, including Mark Pilgrim, has identified any persistence of copyrightable expressive material from earlier versions in chardet 7.0.0.
Richard Fontana states that no one has articulated a viable alternate theory of license violation regarding chardet 7.0.0.
Richard Fontana is presented as an LGPLv3 co-author weighing in on the chardet relicensing situation.

Richard Fontana states that he currently sees no basis for concluding that chardet 7.0.0 is required to be released under the LGPL.
Richard Fontana states that no one, including Mark Pilgrim, has identified any persistence of copyrightable expressive material from earlier versions in chardet 7.0.0.
Richard Fontana states that no one has articulated a viable alternate theory of license violation regarding chardet 7.0.0.
Richard Fontana is presented as an LGPLv3 co-author weighing in on the chardet relicensing situation.

What concrete, example-level evidence (if any) shows that chardet 7.0.0 retains copyrightable expressive material from earlier LGPL-licensed versions?
Has any party produced a detailed, written legal analysis arguing that LGPL obligations apply to chardet 7.0.0, and if so, what theory does it rely on?
What is the provenance of the chardet 7.0.0 codebase (contributors, rewrite claims, and any reuse boundaries), and is that provenance documented in a way that is independently verifiable?
Have there been any formal actions (e.g., compliance notices, takedown demands, or litigation threats) related to chardet 7.0.0 licensing, and what specific allegations do they make?
What is the exact basis for presenting Richard Fontana as an LGPLv3 co-author in this context, and does the corpus source provide verifying references?

If the view that chardet 7.0.0 is not subject to LGPL obligations gains acceptance, licensing compliance uncertainty for organizations using or distributing chardet 7.0.0 could diminish.
Absent concrete evidence of carryover of copyrightable expressive material, potential legal overhang tied to relicensing claims may remain largely reputational and procedural rather than enforceable.

Publication of concrete, example-level code comparisons showing chardet 7.0.0 does not retain copyrightable expressive material from earlier LGPL-licensed versions.
A detailed, written legal analysis concluding LGPL obligations do not apply to chardet 7.0.0, including a clear explanation of provenance and reuse boundaries with independently verifiable documentation.
No formal compliance notices, takedown demands, or litigation threats emerging, or any such actions being withdrawn without specific allegations of retained expressive material.

Concrete evidence showing identifiable, copyrightable expressive material from earlier LGPL-licensed versions persists in chardet 7.0.0.
A detailed, written legal theory asserting LGPL obligations apply to chardet 7.0.0 that is not dependent on contested or unsubstantiated carryover claims.
Formal actions such as compliance notices, takedown demands, or litigation threats alleging specific LGPL violations tied to chardet 7.0.0 code provenance or reuse.