
CODE (Certified Open Source Developer for Enterprise) is a beginner-level, multiple-choice certification on using and contributing to open source safely at work. Open source experts from the Linux Foundation, the Open Source Initiative (OSI), the TODO Group and FINOS created it. It covers how open source projects work, licences and compliance, safe use of dependencies (supply chain and SBOMs), contributing upstream, and how company open source program offices (OSPOs) run. Many GCCs and product companies in Hyderabad have OSPOs and strict rules on which open source developers may use, so knowing them helps freshers and developers get through code reviews and audits.
This guide follows the official CODE exam page. It covers the exam facts, the five domains and their weightings, a licence cheat sheet, a supply-chain checklist, a 3-week plan and 15 original practice questions.
Quick facts (Linux Foundation, November 2026)
| Item | Detail |
|---|---|
| Format | Online, proctored, multiple choice |
| Duration | 90 minutes |
| Price | US$250 for the exam; US$299 with the LFD221 course; US$495 with a THRIVE-ONE subscription |
| Included | One retake; 12 months to take the exam |
| Prerequisites | None |
| Validity | 2 years |
Read the official CODE exam page. The course LFD221, Open Source Essentials for Developers, covers the same ground.
Domains and weightings
| Domain | Weight | Competencies |
|---|---|---|
| Consuming Open Source Software | 28% | Codebase risk; maintenance plans; the software supply chain; dependencies; approval processes; SBOMs |
| Fundamentals of Open Source Software Development | 24% | Issues and pull requests; code reviews; open source principles; communities; release management and semantic versioning |
| Contributing to Open Source | 22% | Contribution strategy; code and documentation practices; copyright and IP; contribution risks; business, personal and open source projects; approval processes |
| Open Source Licensing and Usage Guidelines | 14% | IP, licensing and legal basics; licence compliance including copyleft; risk assessments; export control; CLAs and the DCO |
| Open Source Management Operations | 12% | Contributing upstream; developer support; open source management roles and escalation paths |
Licence cheat sheet
| Type | Examples (SPDX ID) | Main obligation |
|---|---|---|
| Permissive | MIT, BSD-3-Clause, Apache-2.0 | Keep copyright and licence notices; Apache-2.0 also has a patent grant and asks you to note changes |
| Weak copyleft | LGPL-2.1, MPL-2.0, EPL-2.0 | Share changes to the licensed files or library itself; your separate code can stay under its own licence |
| Strong copyleft | GPL-2.0, GPL-3.0 | If you distribute a combined work, release its source under the same licence |
| Network copyleft | AGPL-3.0 | Like GPL, and it also applies when users interact with the software over a network |
This table is for learning only. Real licence decisions belong to your company's OSPO or legal team.
Supply-chain checklist for a new dependency
- Licence is on your company's approved list (check the SPDX identifier).
- The project is maintained: recent releases, active maintainers, issues answered.
- There are no known critical vulnerabilities, and it has a security policy (for example, check its OpenSSF Scorecard).
- The version is pinned, and transitive dependencies are reviewed.
- It is recorded in the SBOM (SPDX or CycloneDX format).
- Someone owns updates, as part of a maintenance plan.
# sign off a contribution under the Developer Certificate of Origin
git commit -s -m "fix: handle empty config file"
# adds: Signed-off-by: Your Name <you@example.com>
# semantic versioning: MAJOR.MINOR.PATCH
2.4.1 → 2.4.2 bug fix
2.4.1 → 2.5.0 new feature, backwards compatible
2.4.1 → 3.0.0 breaking change
3-week study plan
| Week | Focus | Hands-on |
|---|---|---|
| 1 | Open source principles, communities, issues, pull requests, code review, semantic versioning | Fix a "good first issue" in a project you use and open a pull request |
| 2 | Licences, copyleft compliance, CLAs vs the DCO, export control basics, risk assessment | Find the licences of every dependency in one of your projects |
| 3 | Supply chain, SBOMs, approval processes, maintenance plans; contributing upstream; OSPO roles; review | Generate an SBOM for a project and check it for known vulnerabilities; book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. What makes software "open source" under the OSI definition?
Its licence allows anyone to use, study, change and redistribute it, including commercially, without discrimination.
2. Which licence type requires sharing source code for combined works you distribute?
Strong copyleft, such as the GPL.
3. Why do companies treat AGPL code carefully?
Its obligations can apply when users only access the software over a network, as with a SaaS product.
4. What does Apache-2.0 add compared with MIT?
An explicit patent grant, with that grant ending if you sue over patents in the software.
5. CLA vs DCO?
A CLA is a signed legal agreement granting rights to the project; the DCO is a statement contributors accept by signing off each commit.
6. What is an SBOM?
A Software Bill of Materials: a list of every component and version in a piece of software.
7. Name two SBOM formats.
SPDX and CycloneDX.
8. What is a transitive dependency?
A package your direct dependency needs, which you inherit without adding it yourself.
9. Under semantic versioning, which number changes for a breaking change?
MAJOR.
10. Why contribute fixes upstream instead of keeping a private fork?
It avoids the cost of maintaining a fork and of merging every upstream release into it.
11. Before contributing to an outside project from work, what should you check?
Your company's contribution policy and approval process, who owns the copyright, and whether the code contains confidential material.
12. What is an OSPO?
An Open Source Program Office, which sets company policy for using, contributing to and releasing open source.
13. What makes a pull request easy to review?
It is small, focused and linked to an issue, with a clear description and tests.
14. Why can export control apply to open source?
Some technologies, such as certain encryption, have export rules, although published open source often has exemptions.
15. A dependency's only maintainer has stopped responding. What is the risk?
Vulnerabilities may never be fixed, so plan to replace it, fork it or help maintain it.
Before and after CODE
- Learn Git and GitHub with GH-900 GitHub Foundations, then supply-chain security with GH-500.
- Go deeper into supply chain security with CKS or software security with CSSLP.
- Learn development and DevOps hands-on in our Python course and DevOps course; see live developer jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches Python, DevOps, cloud and AI with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the CODE certification?
Certified Open Source Developer for Enterprise, a Linux Foundation exam on using and contributing to open source safely at work.
How long is the CODE exam and what does it cost?
90 minutes of multiple-choice questions, US$250, with one retake.
What are the CODE domains?
Consuming Open Source Software 28%, Fundamentals 24%, Contributing 22%, Licensing and Usage Guidelines 14%, Management Operations 12%.
Who created CODE?
Open source experts from the Linux Foundation, OSI, the TODO Group and FINOS.
Are there prerequisites?
No.
How long is CODE valid?
2 years.



