Open-source project
freeCodeCamp/freeCodeCamp avatar
freeCodeCamp/freeCodeCamp

freeCodeCamp/freeCodeCamp: what the repository is, and how to run it locally

GitHub describes it as freeCodeCamp.org's open-source codebase and curriculum. Learn math, programming, and computer science for free.. The repository metadata lists TypeScript as its primary language. The metadata lists the BSD-3-Clause license. This article stays within the project description and details documented in the GitHub repository README.

459,173 stars47,473 forksTypeScriptBSD-3-Clause

At a glance

What is it?
The freeCodeCamp repository holds both the platform and the curriculum, built as a pnpm and Turborepo monorepo. It is a codebase to contribute to, not a package to install, and the README points learners at freeCodeCamp.org instead.
Who is it for?
Adopt this repository if you intend to contribute curriculum, fix platform bugs, or run a local copy of the freeCodeCamp.org stack for development. Do not clone it expecting an installable learning app or an offline course player; the README sends learners to freeCodeCamp.org, and the repository does not document an offline mode.
Can I use it commercially?
Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • freeCodeCamp/freeCodeCamp459,173 ★ · +5,215
Star history
Repository2026-08-132026-11-15
freeCodeCamp/freeCodeCamp454k459.2k

5,215 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What this repository actually is, and who it is for

The name is easy to misread. freeCodeCamp.org is the learning site; freeCodeCamp/freeCodeCamp is the open-source codebase and curriculum that runs it. The README describes the organisation as a donor-supported 501(c)(3) charity and the site as a self-paced curriculum with thousands of interactive coding challenges. The repository is the machinery behind that site, written primarily in TypeScript and organised as a monorepo: api/, client/, curriculum/, packages/, tools/, e2e/ and docker/ sit at the top level next to pnpm-workspace.yaml and turbo.json. The homepage field in package.json points at contribute.freecodecamp.org rather than the learning site, which tells you who the repository is addressed to.

So the audience is contributors and people who want to understand or run the platform: someone fixing a challenge description, adding a lesson, changing the client UI, or working on the API. Learners who want the courses go to freeCodeCamp.org and never touch this code. That split matters for every decision that follows, because almost every question about installation, dependencies and licensing here is a contributor question, not a student question.

The curriculum itself is content, not just code. The README states that learning resources in the /curriculum directory, including their subdirectories, are copyright © 2014 freeCodeCamp.org, and the licence section separates that from the software licence. If you plan to reuse lesson text elsewhere, that distinction is the first thing to read, not the last.

How the monorepo is put together: curriculum, client, api

The layout is a Turborepo workspace. turbo.json and pnpm-workspace.yaml define the build graph, and the root package.json exposes scripts that fan out to the individual workspaces: build:client, build:api and build:curriculum each call turbo with a filter such as -F=@freecodecamp/client. A plain build runs turbo build across the graph. This is a conventional setup for a large TypeScript project, and it means the pieces are built and versioned together from one lockfile (pnpm-lock.yaml) rather than published separately.

The three parts do different jobs. The curriculum package turns the lesson content in curriculum/ into something the client can serve; the clean:curriculum script removes ./curriculum/generated/curriculum.json, which implies a generated artefact is produced during the build. The client is the front end learners see. The api is the back end, and sample.env at the repository root exists to show which environment variables it expects. The tools/ directory holds contributor tooling: the challenge editor is a git submodule, initialised by the challenge-editor-setup script, and challenge-helper-scripts provides create-new-project and create-new-language-block for adding curriculum content.

That structure is the real answer to how freeCodeCamp works at the code level: content is authored in the curriculum directory, compiled into a generated file, served by the client, and backed by the API. The README does not document deployment architecture beyond saying the code runs live at freeCodeCamp.org, so anything about production infrastructure beyond this is not stated in the repository.

Installing the freeCodeCamp codebase locally

There is no published package to install and no npm install freecodecamp step. The entry point is cloning the repository from GitHub. The engines field in package.json sets the floor: node >=24 and pnpm >=12. The .nvmrc file exists so a version manager can pick the right Node version, and the .devcontainer directory suggests a container-based setup is supported, though the README does not walk through it.

Start by cloning and installing dependencies with pnpm, which is the workspace manager the lockfile is written for.

bash
git clone https://github.com/freeCodeCamp/freeCodeCamp.git
cd freeCodeCamp
pnpm install

After install, the root scripts are your entry points. To build and run the development environment, the package.json defines develop, and there is a clean-and-develop script that cleans, reinstalls and develops in one go. If you only want one part, the filtered build scripts are the way in.

bash
pnpm run build:curriculum
pnpm run build:client

The first compiles the curriculum content; the second builds the client workspace. A full build runs turbo build across every workspace. The README does not document the exact port the client or API listens on, so check sample.env and the workspace configuration before assuming a URL.

If you are working on curriculum content, the helper scripts are the intended path rather than hand-editing generated files. The challenge editor is a submodule, so it needs an explicit setup step before it runs.

bash
pnpm run challenge-editor-setup
pnpm run challenge-editor

The first command initialises the submodule and installs its dependencies; the second starts the editor. The create-new-project and create-new-language-block scripts live under tools/challenge-helper-scripts and are the documented way to add new curriculum entries.

Where the local setup gets awkward

The main limitation is scope. This is a full-stack application with a database-backed API, a generated curriculum artefact and a client, and the README does not document a minimal path to a working local instance. sample.env exists, but the README does not list which variables are mandatory, and there is no documented one-command bootstrap. Expect to read the workspace configuration and the contribute.freecodecamp.org guides rather than the README alone. That is normal for a project of this size, but it is a real cost for someone who just wants to read the curriculum source.

A second constraint is the toolchain floor. Node 24 and pnpm 12 are recent majors; a machine pinned to an older Node LTS will fail the engines check or behave unpredictably. The repository also uses a git submodule for the challenge editor, which is a common source of confusion for first-time contributors: a plain clone without submodule initialisation leaves tools/challenge-editor empty, and the dedicated setup script exists precisely because of that.

Finally, this is the wrong tool for several jobs. It is not an offline course player: the README does not document an offline mode, and the learning experience is described as running live at freeCodeCamp.org. It is not a library you can pull into another project. And if your goal is a certificate, cloning the repository does nothing for you; certifications are claimed on the site after completing the required projects and passing the exam.

The curriculum and certifications the repository serves

The README lists the certifications the platform delivers: Responsive Web Design, JavaScript, Front-End Development Libraries, Python, Relational Databases, and Back-End Development and APIs, together forming the Full-Stack Developer Curriculum. Each involves interactive lessons, workshops, labs, reviews and quizzes, with 5 required projects before the exam, and the certification is claimed after passing. There are also language certifications at A2 and B1 English for Developers and A1 Professional Spanish and Chinese, all marked Beta, plus a Foundational C# with Microsoft Certification. The README also mentions The Odin Project (freeCodeCamp Remix), Coding Interview Prep, Project Euler and Rosetta Code as interview preparation material.

For a contributor, this list is a map of the content tree. Adding a lesson means working inside the curriculum directory and using the helper scripts, and the audit-challenges script under curriculum/ exists to check challenge integrity. The README states that certifications can be revoked for violations of the Academic Honesty Policy, which is a policy decision on the site rather than a feature of this codebase, but it explains why challenge validation is taken seriously in the tooling.

The README does not describe how exam grading is implemented in the code, so treat any claim about the exam mechanism beyond what is written here as unverified.

Alternatives, and how they differ in approach

The closest comparison inside the repository is The Odin Project, which the README references as freeCodeCamp Remix and lists among interview preparation resources. Both are free, project-oriented web development curricula, but the difference in approach is what you get from the repository. The Odin Project is described here only as a linked resource, so the honest comparison is narrow: freeCodeCamp ships an interactive platform with in-browser challenges, a generated curriculum artefact, quizzes and a claimable certification, while The Odin Project is referenced as a separate curriculum rather than as part of this codebase.

A second alternative is the site itself. If you want to learn, freeCodeCamp.org is the product; the repository is the source. Choosing the repository over the site only makes sense when you intend to change something. A third option, for people who want a self-hosted course platform, is to look at how this repository separates curriculum content from the client and API, and decide whether that split fits your needs; the README does not present the code as a reusable platform template, and the licence split between software and curriculum content means reuse needs reading LICENSE.md first.

Maintenance, upgrades and licence boundaries

The repository is not archived, and the last push was on 2026-11-11, so it is being worked on. There are no GitHub releases, which fits a continuously deployed web application: there is no versioned artefact to upgrade, only the main branch. Upgrading means pulling main and reinstalling with pnpm, and the clean-and-develop script exists for exactly that situation when stale build output gets in the way. The renovate.json file indicates dependency updates are automated, which reduces the chance of a long-stale lockfile but also means the dependency graph moves under you.

Licensing has two layers, and the README is explicit about both. The computer software is under BSD-3-Clause, which is permissive and allows reuse with attribution; read LICENSE.md for the exact terms. The learning resources in /curriculum are copyright © 2014 freeCodeCamp.org and are not covered by that software licence. If you plan to fork the platform, the code path is straightforward; if you plan to reuse lesson text, the curriculum notice applies. That is a description of what the repository states, not legal advice.

The README also directs security reports through contribute.freecodecamp.org/security/ and bug reports through a forum article before opening a GitHub issue, so the contribution workflow has a documented front door.

Editorial conclusion

Adopt this repository if you intend to contribute curriculum, fix platform bugs, or run a local copy of the freeCodeCamp.org stack for development. Do not clone it expecting an installable learning app or an offline course player; the README sends learners to freeCodeCamp.org, and the repository does not document an offline mode. Before you start, check that Node 24 and pnpm 12 are installed, read sample.env for the environment variables the API expects, and read LICENSE.md, which covers the software under BSD-3-Clause while the /curriculum directory carries its own copyright notice. If your goal is a certificate rather than code, the certifications are claimed on freeCodeCamp.org after the required projects and exam, not from this repository.

Frequently asked questions

What is freeCodeCamp and what does it do?

freeCodeCamp.org is a free, self-paced learning site run by a donor-supported 501(c)(3) charity, offering a full-stack web development and machine learning curriculum with thousands of interactive coding challenges. The repository is the open-source codebase and curriculum that runs that site.

How do I use the freeCodeCamp repository for the first time?

Clone the repository from GitHub, install dependencies with pnpm install, and use the root scripts such as build:client or build:curriculum. The package.json requires Node 24 or later and pnpm 12 or later, and sample.env shows the environment variables the API expects.

How do I get a freeCodeCamp certificate?

According to the README, each certification requires completing interactive lessons, workshops, labs, reviews and quizzes, then 5 required projects, then passing the exam, after which the certification can be claimed on freeCodeCamp.org. Certifications can be revoked for violations of the Academic Honesty Policy.

How do I take the freeCodeCamp exam?

The README states that you qualify for the exam after completing the 5 required projects for a certification, and that for the language certifications you must complete all quizzes in order to qualify. It does not document the exam mechanics in the codebase.

Can I use freeCodeCamp offline?

The README does not document an offline mode; it describes the learning platform as running live at freeCodeCamp.org. Running the repository locally is a development setup for contributors, not a documented offline course player.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/freecodecamp-freecodecamp.svg)](https://hysenlabs.com/projects/freecodecamp-freecodecamp)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/freecodecamp-freecodecamp.svg)](https://hysenlabs.com/projects/freecodecamp-freecodecamp)

Was this useful?