The License Header a CTO Removed: A Q&A on One Open Source Decision
Archi3 min read
The Decision to Strip License Headers#
When a mid-sized fintech company forked an open source library to add features, its CTO made a call: remove the license headers from every file. The reasoning seemed sound at the time. The company had rewritten most of the code, and the headers cluttered the source. But the decision came back to bite them. In this Q&A, the CTO explains what happened and what they learned.
Q: What was the library, and why did you fork it?
A: It was a widely used JSON parsing library under the Apache License 2.0. We needed faster handling of large payloads for our real-time fraud detection system. The original project was slow to merge pull requests, so we forked it and made our own changes. We added a streaming parser and shaved about 40 milliseconds off each transaction. That mattered because we process around 2,000 transactions per second at peak.
Q: At what point did you decide to remove the license headers?
A: After about six months. Our fork had diverged significantly. We had replaced the core parsing logic and added new modules. The headers, which listed the original authors and the Apache license, felt like noise. Our legal team said we were fine as long as we included the license file in the distribution. So we stripped the headers from files we had substantially rewritten. We kept the license file at the root of the repository. That was our interpretation of the license terms.
Q: What went wrong?
A: A developer on our team posted a snippet of our modified code to a public forum. Someone noticed the missing headers and flagged it. The original project maintainers saw it and sent a cease-and-desist letter. They claimed we violated the license by removing attribution. Our legal team disagreed, but the reputational damage was immediate. A blog post about it got picked up by a few newsletters. We had to issue a public statement and restore the headers within a week.
Q: How did you handle the fallout internally?
A: It was embarrassing. Our engineering team spent two days restoring headers across 1,200 files. We had to audit every file to determine which ones were substantially rewritten and which were not. That was harder than it sounds because we had not tracked changes at the file level. We ended up restoring headers on all files to be safe. The whole episode cost us about 80 engineering hours and a lot of goodwill.
Q: What did you learn about license compliance?
A: The main lesson is that license headers are not just decoration. They are a legal requirement under many licenses, including Apache 2.0, which requires retaining attribution notices. Our legal team's interpretation was technically defensible, but the risk was not worth it. We now have a policy: never remove license headers, even from files we rewrite completely. We also added a check in our CI pipeline that flags any file missing a header. That check has caught a few mistakes since.
Q: Would you fork again?
A: Yes, but differently. We would contribute our changes upstream first. In this case, the maintainers were actually open to our streaming parser. They had been busy with other things. We could have avoided the fork entirely. Now we have a rule: before forking, we try to work with the upstream project for at least three months. If that fails, we fork with a clear plan for license compliance and a commitment to contribute back.
Q: What advice do you have for other companies considering a fork?
A: Treat license compliance as a first-class engineering requirement, not an afterthought. Document every change you make and keep a record of which files you modify. Use a tool like FOSSA or ScanCode to automate license scanning. And involve legal early, but do not rely on them to catch everything. Engineers need to understand the licenses of the code they use. We now include license training in our onboarding. It takes an hour and saves a lot of pain.
Q: How has this changed your open source strategy?
A: We are more deliberate. We have a formal open source review process for any new dependency. We also contribute more. Last year we upstreamed 15 patches to various projects. That reduces the need to fork and builds goodwill. The incident was a wake-up call. It made us realize that open source is not free; it comes with obligations. We take those seriously now.
More articles