Rakuten AI Stumbles in Open Source Controversy

Japan's e-commerce giant Rakuten has landed in the middle of an open-source storm following the release of its much-touted Rakuten AI 3.0 model. What was supposed to be a showcase of Japanese AI innovation instead became a case study in how not to handle open-source dependencies.

The Missing License That Sparked Outrage

Tech enthusiasts quickly noticed something amiss when examining Rakuten's "Japan's largest" AI model. The system appeared built upon DeepSeek-V3, a common enough practice in AI development. But someone had conveniently forgotten to include the original MIT Open Source License file - a critical requirement for any derivative work.

"It's like removing the copyright page from a book you didn't write," commented one developer on GitHub. The open-source community reacted swiftly, flooding forums with criticism about what many saw as an attempt to obscure the model's origins.

Public Backlash Compounds the Problem

The controversy hit particularly hard in Japan, where netizens expressed disappointment that government-funded computing resources had apparently produced what looked like repackaged technology. Comments on social media ranged from technical critiques to emotional appeals about national pride in innovation.

Rakuten moved quickly to contain the damage:

• Added a NOTICE file containing DeepSeek's original statement
• Reinstated all required license information
• Technically returned to compliance with MIT requirements

But as one community moderator noted, "Legal compliance doesn't equal ethical behavior. The optics here are terrible."

Questions Remain About Development Process

The incident raises broader questions about how companies balance:

• Transparency in acknowledging open-source foundations
• Proper attribution when building on others' work
• Responsible use of public research funding

While Rakuten has corrected the license issue, they've yet to explain why it was removed initially - leaving many wondering if this was oversight or intentional obfuscation.

The tech community continues debating where to draw lines between: ✅ Acceptable use of open-source models 🚫 Attempts to claim unearned credit 💸 Particularly when public funds are involved

Key Points:

• Rakuten AI 3.0 omitted required MIT license for DeepSeek-V3 foundation
• Quick corrections made after community outcry
• Japanese netizens question use of government resources
• Incident highlights ongoing tensions in open-source attribution