On Open Source Ethics

Claude Code's source code was recently leaked. And in its wake, a few incidents have been unfolding in the open source community.

What happened

Someone created a GitHub repository based on the leaked Claude Code source. The person behind it has already been identified. As expected, the reaction was explosive — stars poured in within hours.

Then something unbelievable happened. The repository's Git history was rewritten via force-push, and the project's subject was changed entirely. What remained was nothing more than a badge: "a project that gained massive stars in record time."

What matters more than the leak itself

The leak of Claude Code's source is unfortunate. There were likely things Anthropic could have done to prevent it. But what draws my attention more than the leak itself is a different question.

What ethical standards should we hold when working on open source?

Open source software has a reach that extends far beyond developers — even non-developers rely on it. Star counts serve as a proxy for project credibility. People look at those numbers when deciding whether to add a dependency to their own projects. Deliberately manipulating that trust is hard to justify, regardless of whether it happens in an open source context or elsewhere.

Deceiving your audience is difficult to defend no matter who they are.

The viral play worked — but

If the goal was "getting attention through viral marketing," then it unequivocally succeeded. People noticed. People are talking. But was it the right approach? I don't think so.

The reaction in Korean developer communities like GeekNews has been damning. The overwhelming consensus is criticism, and trust in the people behind the project has cratered. No surprise there.

The numbers went up in the short term, but trust in the community is hard to recover. The open source ecosystem ultimately runs on trust. Every part of the process — publishing code, reviewing it, contributing to it — operates under the assumption that participants are acting honestly. They undermined that assumption themselves.

Professionals are professionals

Everyone who does this for a living is a professional. That doesn't change.

Professionals work in front of an audience — their users. The audience is what drives motivation, what pushes us toward better output. And if that's the case, you don't deceive your audience. There's a baseline set of principles that come with being a professional, and one of them is being honest about your work.

Whether you're contributing to open source or writing code at a company, someone is going to use what you build. Basic respect for that someone — that's the line we should be holding.