惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
H
Hackread – Cybersecurity News, Data Breaches, AI and More
腾讯CDC
F
Fortinet All Blogs
I
InfoQ
Jina AI
Jina AI
有赞技术团队
有赞技术团队
A
About on SuperTechFans
Stack Overflow Blog
Stack Overflow Blog
小众软件
小众软件
Recent Announcements
Recent Announcements
aimingoo的专栏
aimingoo的专栏
雷峰网
雷峰网
B
Blog RSS Feed
C
Check Point Blog
Y
Y Combinator Blog
博客园 - 聂微东
云风的 BLOG
云风的 BLOG
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Hugging Face - Blog
Hugging Face - Blog
Microsoft Security Blog
Microsoft Security Blog
Engineering at Meta
Engineering at Meta
G
Google Developers Blog

Danb Blog

August 2026: What I've Been Working On · Danb Blog Great Tech: Intel 2500k CPU · Danb Blog July 2026: What I've Been Working On · Danb Blog My Experience with Ubuntu Desktop 26.04 · Danb Blog Thumbnails for Orca 3MF in GNOME Files · Danb Blog Cheaper Sodastream Gas with a Big Tank · Danb Blog June 2026: What I've Been Working On · Danb Blog Running Snyk On Forgejo/Codeberg Actions · Danb Blog Tuta & Proton: An Open Source Client Does Not Result in an Open Source Service · Danb Blog May 2026: What I've Been Working On · Danb Blog 3D Printing Parts for my Greenhouse, Round 2 · Danb Blog Great Devices: Nexus 7 2013 · Danb Blog R36S Console RetroArch Stuck Menu Issue · Danb Blog April 2026: What I've Been Working On · Danb Blog Basic OpenCode Sandboxing with Docker · Danb Blog Games Played in 2025 · Danb Blog March 2026: What I've Been Working On · Danb Blog Shivam Mathur's "node-docker" Images are Awesome for PHP CI · Danb Blog February 2026: What I've Been Working On · Danb Blog Your BookStackApp project was assigned as a project for my Software Architecture course · Danb Blog My Sovol SV08 3D Printer Setup in 2026 · Danb Blog January 2026: What I've Been Working On · Danb Blog Epson Printer: The administrator password you entered was not recognized · Danb Blog Pressure to Follow Process · Danb Blog Online Shopping Email Notifications · Danb Blog My HomeLab Setup in 2026 · Danb Blog Linux Label Printing with the Phomemo D30 · Danb Blog Reporting to the CMA: Google Android Developer Verification · Danb Blog OPNsense & Dnsmasq: Responding with specific DNS servers · Danb Blog An Impromptu Introduction to ZFS Drive Replacement at 1am · Danb Blog
LLMs are Directing Open Source Licensing · Danb Blog
2025-01-07 · via Danb Blog

I’m often looking at the licensing of open source projects, either out of personal interest or while moderating posts to /r/opensource, and through this I’ve seen a recent trend of projects having something like this in their readme:

## License

MIT License - See [LICENSE](LICENSE) file for details

But the interesting part is that the referenced LICENSE file is frequently missing. This wouldn’t be surprising as a one-off, but I was seeing this many times per week, all in a similar format, all MIT licensed.

I suspected the rising use of LLMs as the cause, so I started to query this with authors, which confirmed my suspicions. Examples: A, B, C, D. I queried others too but there often seems to maybe be a little hesitance by authors to directly confirm their use of an LLM, so I get an indirect response. Examples: A, B.

Since it’s always MIT, I worry a little about how this trend may further reduce opportunity for other licensing options to be considered while further popularising this single very permissive license. Through a cynical lens, I could theorize that maybe this is purposeful to keep project licenses friendly to the large companies creating these LLMs, who tend to hiss back at the sign of a copyleft license. Realistically though, the MIT license is probably generated due to its very high popularity, being the most used license on GitHub (where I guess most LLMs would have been trained on) by quite a margin.

This situation does raise some questions for me though: Are authors really understanding the terms they’re applying when an LLM is choosing their license? If not, could this create more conflict from scenarios where users exercise license rights which the author doesn’t like/expect? Are licensing requirements of included/dependant software being ignored due to this? How strong is the bias towards MIT?

Ultimately it’s up to the author to understand and take responsibility for what they’re publishing, even if using an LLM to help them along but, with this often being overlooked already, I’m expecting we’ll see more “dawg i chatgpt’d the license” moments in the future.