enkidevs/curriculum: the open source learning content behind Enki
👩🏫 👨🏫 The open-source curriculum of Enki!
At a glance
- What is it?
- This repository holds the Enki curriculum as plain files: one folder per subject, from javascript and python to blockchain and generative-ai. It is a content base for contributors and for anyone building a learning app, licensed for non-commercial use only.
- Who is it for?
- Adopt this repository if you want a broad, already-written curriculum you can remix for non-commercial teaching, or if you plan to contribute through the wiki workflow. Do not adopt it if you need a packaged library with a versioned API, a permissive commercial licence, or published release notes: there are none.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 53 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What enkidevs/curriculum is, and who it is for
Enki is a learning app, and enkidevs/curriculum is the content that sits behind it, published openly. The README frames the project as a community effort: the curriculum is "entirely open-source" and available to edit, comment on and contribute to. That sentence defines the audience more precisely than any feature list. This is not a library you import. It is a body of teaching material that a community maintains in the open, and the primary consumers are contributors and people who want to reuse the material, not applications that call it at runtime.
The repository is organised by subject rather than by format. The top level contains directories such as javascript/, python/, sql/, security/, git/, linux/, react/, typescript/, docker/, go/, java/, kotlin/, swift/, cpp/, csharp/, r/, lua/, mongodb/, regular-expressions/, comp-sci/, tech-interviews/, data-analysis/, python-data-analysis/, spreadsheets/, web/, coding-intro/, blockchain/, intro-to-nfts/, generative-ai/, nocode-webflow/, zapier/, airtable/ and glossary/. There is also a .archived/ directory, which tells you the project retires content by moving it aside rather than deleting it.
The topics listed on the repository are broad: ai, algorithms, blockchain, chatgpt, computer-science, css, curriculum, data-science, education, enki, git, gpt4, html, java, javascript, learn-to-code, linux, python, security, sql. If you are a teacher who wants a starting point for an intro course, or a developer building a learning product and unwilling to write every lesson from scratch, the breadth is the reason to look here first.
How the content is laid out and how contributions flow
The mechanism is deliberately unglamorous: content lives as files in subject directories, and changes arrive as pull requests. The README points contributors at the project wiki for instructions, and the layout confirms the model. There is no build step described in the README, no package manifest at the top level, and no documented generation pipeline. The repository is the source of truth, and the wiki is the manual.
Governance is stated explicitly. The project has adopted the contributor covenant as its code of conduct, and the README says the rules will be enforced, pointing questions to content-team@enki.com. It also cites The Recurse Center's social rules as a fuller explanation of the environment the project wants. That combination, a written code of conduct plus a named contact, is more than many content repositories offer, and it matters here because the contribution surface is prose and exercises, not code that a test suite can validate.
The CHANGELOG.md at the top level is the only change history visible in the repository listing. There are no retrieved releases, so there is no versioned artifact to pin against. If you fork the content, you are forking a moving target.
Getting the curriculum: clone the repository and read a track
There is no install step, because there is no software to install. The README's only instruction for getting started is to look at the wiki, and the repository is fetched the way any GitHub repository is. The README itself does not print a clone command, so the URL below is the repository URL from the project's own page rather than a documented install step.
git clone https://github.com/enkidevs/curriculum.gitOnce the working copy is on disk, the first real use is browsing. The top-level entries are the tracks: javascript/, python/, sql/, security/, git/, linux/, react/, typescript/, docker/, go/, java/, kotlin/, swift/, cpp/, csharp/, r/, lua/, mongodb/, regular-expressions/, comp-sci/, tech-interviews/, data-analysis/, python-data-analysis/, spreadsheets/, web/, coding-intro/, blockchain/, intro-to-nfts/, generative-ai/, nocode-webflow/, zapier/, airtable/ and glossary/, alongside .archived/, CHANGELOG.md, LICENSE.md and README.md.
The README does not document the internal file format of a lesson, so what sits inside a track is something you have to inspect yourself. If you intend to contribute rather than consume, the README sends you to the wiki at https://github.com/enkidevs/curriculum/wiki for the workflow, and the code of conduct governs how you interact once you are there. Anything beyond fetching and browsing is described on the wiki, not in the README, and this article will not guess at it.
The licence is the real constraint here
The repository's licence field reads NOASSERTION, but the README is explicit: the work is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International. The README's own plain-language summary says you cannot charge other people to use it or use it to make money, but you can use it to help people learn and you are free to remix or adapt it, provided you attribute Enki and the author of the work.
That single clause decides most adoption questions. ShareAlike means an adapted version carries the same licence forward, so you cannot take these lessons, rework them and release the result under a permissive licence. NonCommercial means a paid course or a commercial product built on this content is outside the grant. The README says the licence text lives in LICENSE.md, and that file is the authoritative wording, not the summary. This is not legal advice; if your use is commercial or ambiguous, read LICENSE.md and get proper advice.
The practical consequence is that enkidevs/curriculum is a good fit for non-profit teaching, internal training at a non-commercial organisation, or a free learning project, and a poor fit as the content base for a paid product. That is a design choice, not an oversight, and the README states it plainly.
Where the repository is thin: no releases, stale corners, silent details
The most useful thing a reviewer can say about this project is what it does not provide. There are no retrieved releases, so there is nothing to pin, no semantic version to track and no upgrade path to reason about. The README does not document a content schema, a validation step, or how the mobile app consumes these files. The homepage points at https://www.enki.com/mobile-app, which is the product, not documentation of the content format.
The .archived/ directory is the clearest signal of maintenance reality. Content gets retired, and retirement means relocation rather than removal. If you depend on a specific track, check whether it still sits at the top level before you build a course around it. The CHANGELOG.md is the only changelog, and the README does not describe a deprecation policy or a compatibility promise for content that moves.
There is also a mismatch between the repository's scope and its documentation. Topics span blockchain, generative-ai and tech-interviews, but the README is a short welcome note about community and conduct. It does not explain how a lesson is structured, how translations or forks are handled, or what the review bar is for a pull request. The wiki is where that presumably lives, and the README defers to it. For a content repository of this breadth, that gap is the main friction a new contributor will hit.
Alternatives, and how the approach differs
The obvious comparison is freeCodeCamp's curriculum repository, which is also open source and also organises learning material in a large public repository. The difference is in the coupling: freeCodeCamp's curriculum is tied to a platform with its own build and test tooling, so contributing means working within that toolchain. Enki's repository is presented as content first, with the wiki as the workflow guide and no build pipeline described in the README. If you want to lift lessons into your own product, the looser coupling helps; if you want automated validation of exercises, it does not.
A second comparison is a general-purpose content platform such as an LMS or a docs generator. Those give you a schema, a renderer and a versioning story, and they give you nothing to teach. enkidevs/curriculum is the inverse: it gives you the teaching material and leaves the rendering, versioning and packaging entirely to you. Choosing between them is choosing whether you want to write content or write the system around content.
The licence is the third axis. Many open curriculum projects ship under permissive terms that allow commercial reuse. This one does not, and the README says so in the first paragraph of the licence section. If commercial reuse is a requirement, that difference alone rules this repository out regardless of content quality.
Maintenance, upgrades and what to verify before adopting
The repository is not archived, and the last push was on 2026-07-25, so there is recent activity. There are no releases, which means upgrades are not versioned events. You track the master branch, or you fork and pull changes when you want them. For a content repository that is a reasonable model, but it puts the burden of noticing change on you: the CHANGELOG.md and the commit history are the only signals, and the README does not promise stability for any particular track.
Cost of adoption is mostly review time. You need to read the material in the tracks you care about, confirm the licence in LICENSE.md covers your use, and check that the folder you want has not been moved into .archived/. Those three checks are cheap and they answer the questions that actually block adoption.
If you plan to contribute rather than consume, the entry cost is the wiki plus the contributor covenant. The README names content-team@enki.com as the contact for conduct questions, which is a concrete escalation path rather than a vague promise of community support.
Editorial conclusion
Adopt this repository if you want a broad, already-written curriculum you can remix for non-commercial teaching, or if you plan to contribute through the wiki workflow. Do not adopt it if you need a packaged library with a versioned API, a permissive commercial licence, or published release notes: there are none. Before you build on it, verify the licence terms in LICENSE.md against your own use, and check the state of the folder you care about, since .archived/ shows that parts of the content have been retired rather than deleted.
Frequently asked questions
What is enkidevs/curriculum?
It is the open source curriculum behind the Enki learning app, published as subject folders such as javascript/, python/, sql/ and security/. The README describes it as entirely open-source content that anyone can edit, comment on and contribute to.
How do I access the enkidevs/curriculum content?
The repository is public on GitHub and the README's only getting-started pointer is the project wiki at https://github.com/enkidevs/curriculum/wiki. There is no package to install and no build step described in the README.
What licence does enkidevs/curriculum use?
The README states the work is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International. In the README's words, you cannot charge others to use it or use it to make money, but you can remix and adapt it with attribution to Enki and the author.
Can I use enkidevs/curriculum in a commercial product?
The README's plain-language summary of the licence says you cannot use it to make money, and ShareAlike requires adaptations to carry the same licence. The authoritative terms are in LICENSE.md, not the summary, so check that file before relying on it.
How do I set up enkidevs/curriculum for contributing?
The README directs new contributors to the wiki for instructions and states that the project has adopted the contributor covenant as its code of conduct. Questions or concerns go to content-team@enki.com.
Is enkidevs/curriculum still maintained?
The repository is not archived and the last push was on 2026-07-25. There are no retrieved releases, so changes arrive on the master branch rather than as versioned artifacts.
Community notes