How Much Open Source Is in Your Builds?

Many business leaders think of open source as software their organization chooses to install, such as Linux or Firefox. Yet open source is a critical element of the software applications their teams create. In this video, Sonatype CTO and co-founder Brian Fox explains why open source is easy to overlook, how modern build tools bring it into your software, and why teams rely on it to build better applications without starting from scratch.

glyph bracket orange
glyph bracket orange

Frequently Asked Questions

What is open source software?

Open source is software whose source code is available under a license that lets people use, inspect, modify, and share it, subject to the license terms. Developers use open source libraries, frameworks, and tools to build on existing work instead of starting from scratch.

How is open source different from proprietary software?

Open source makes its source code available under a license that permits certain uses and changes. Proprietary software is controlled by its owner, who sets the terms for access and use. Both types of software can be part of the same application.

Do internally developed applications use open source?

Yes. Internally developed applications often rely on open source libraries, frameworks, and other components. Teams may add them directly or bring them in through other dependencies, and AI coding agents can also recommend or add them. So even software built in-house can include a substantial amount of open source.

Why do organizations use open source?

Open source gives teams access to existing software they can build on, saving time and effort while letting them focus on what’s unique to their applications. It also underpins agentic development: AI agents can select and add open source dependencies as they help create software. When teams use agentic workflows, open source becomes one of the primary building blocks in their builds.