IELTS Atlas: GPL-3.0 code, a question bank you have to bring yourself
An IELTS reading and listening practice system supporting question-bank browsing, full-test practice, score records, mistake analysis, data backup and local question-bank import.
At a glance
- What is it?
- sallowayma-git/IELTS-practice is a pure frontend IELTS reading system that runs from index.html over file protocol, with practice records kept in browser local storage. The code is GPL-3.0, and every piece of exam content is deliberately left out of the repository and the release packages.
- Who is it for?
- This suits a learner who wants practice material they control on their own machine, and it is a poor fit for anyone planning to publish a question bank site or a paid community, which the usage notice rules out in as many words. Three things to check before you start.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly JavaScript, 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.
Star history
- sallowayma-git/IELTS-practice2,282 ★ · +938
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| sallowayma-git/IELTS-practice | 1.3k | 2.3k |
938 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two product names, two READMEs, and a tag called v0.6.2-fix
The repository carries two names for one thing. The heading reads IELTS Atlas / IELTS Practice, while the overview section introduces the product as IELTS Atlas and nothing after that uses the second name. The repository description is written in Chinese and describes an IELTS reading and listening practice system with question bank browsing, full test practice, score records, mistake analysis, data backup and local question bank import. Documentation is split the same way: an English `README.md` and a `README.zh-CN.md`, linked side by side at the top. Release notes live in the tree rather than on the release page, with `RELEASE_NOTE-0.6.3.1.md` committed at the root, while the release titles themselves carry nothing but the tag, `v0.6.3.1`. Tag naming is not consistent either: the three recent tags are `v0.6.3.1`, `v0.6.3` and `v0.6.2-fix`, and that last one puts a suffix where the others have a fourth version number. The newest tag and the last push share the same timestamp, 2026-10-02.
GPL-3.0 for the code, and nothing granted for the content
The licensing is split in two on purpose, and the split is stated at the top of the file before anything else. The code is governed by `LICENSE`, which the metadata records as GPL-3.0. Question sources, articles, audio, PDFs, images and other third-party content remain the property of their original copyright holders and are recommended for personal study and exam preparation only. The usage notice then spells out what that permits: running locally, self hosting, or deploying to a personally controlled web environment for learning, research and personal use, on your own computer, a private server, a NAS or personal web space, as long as access and distribution stay under your control. What is prohibited is public redistribution of websites, mirrors or archives carrying question sources, audio, PDFs, explanations, modified pages or packaged builds, plus commercial sales, paid communities, traffic generation and promotion. The reason given is not only legal: large scale distribution raises the chance of complaints, takedown reports, repository deletion or page closure, which would hurt every user.
Three branches, and a table with three empty columns
The branch overview describes three lines of work that are not variations of one product. `main` is the static web edition, pure frontend, said to run on almost any device. `feature/multi-device-easy-deploy` is a self-hosted server edition with multi-device data sync, aimed at users with some technical background. `IELTS-WRITING-FEAT` is described as an AI-native collaboration client with AI powered writing scoring, reading coaching and self-evolution. The table carries Status, Maturity and Tech columns and none of the three has a single entry, so the file asks you to trust the prose descriptions for all comparison. A second table points at a related repository, an integrated standalone web server solution with backend, routing, database and security infrastructure, hosted under a different account at `k-undurkhaan-2`. Its link text carries an invisible word joiner character between two words of the project name, which is why the name renders oddly when copied and does not match a plain search for it.
index.html is the only door, and the score comes back through a second window
The single entry point is `index.html`, and the instruction is explicit that older entry pages named in legacy documents no longer work. You download and extract the whole project, keep the directory hierarchy intact rather than copying `index.html` on its own, open that file, and confirm the question list loads in the library page. Practice pages then open in a new window, which is why the requirement section tells you to use a recent stable Chrome or Edge and to allow pop-ups when prompted. That window is also where the data path is fragile: if a practice opens but the score is not saved, the file points at pop-up permissions, console errors and cross-window messaging, in that order. Records live in browser local storage by default, so the app runs straight off the file protocol. When a browser restricts file resources, the fallback is to serve the project root with `python -m http.server 8000` and open `http://localhost:8000/`.
The generated index is the contract, and it says not to edit it
Reading practice is built on two generated directories, `assets/generated/reading-exams/` for the exams themselves and `assets/generated/reading-explanations/` for explanations. The file states that the default reading index is generated under `assets/generated/` and should not be hand-edited, which puts the index under the same control as the build rather than the user. Listening works differently: those indexes are produced by a browser-side scan when you import your own resources. The library page is where configuration happens, with filtering by type (All, Reading, Listening) and by category (P1, P2, P3), search across title, filename or metadata, sorting by practice status and progress, and a Settings route for Load question bank, for switching between bank configurations, and for forcing a refresh of the index. So a custom bank is imported as a folder, indexed by the browser, and then selected from Settings rather than edited in place.
Listening is behind a build flag and two hand placed index files
The compliance decision is implemented rather than promised. The public repository and the standard release packages do not contain listening audio, question sources, PDFs, the full `ListeningPractice/` directory, or any pre-generated listening index. To turn listening on locally you supply your own resources and place a generated index at two paths:
assets/generated/listening-exams/manifest.js
assets/generated/listening-exams/listening-index.compat.jsThat setup supports the P1 to P4 structure and unifies listening results into the same record and statistics pipeline as reading through `listening-record-bridge`, which is why the statistics pages do not need a separate listening mode. The file also pre-empts the most common support question by saying that missing files in a public package are expected rather than a defect. For anyone packaging their own material, the switch is a build flag: building with `INCLUDE_LOCAL_LISTENING=1` includes your own `ListeningPractice/P1` through `P4` folder in a personal-use package, so the content ships by decision at build time rather than by download.
Records stay in the browser, which is the reason two other branches exist
Everything the app records goes into browser local storage by default, and the feature list is arranged around that single fact: question bank browsing, reading practice, optional listening practice, full test sets, practice records, score statistics, mistake analysis, data backup, question bank import, vocabulary tools, reading review and achievements. The overview page summarises it as items practised, average performance, study time, streaks and per-category progress, so the streak and the average are computed from one browser profile rather than an account. Reading review mode is not a separate feature: the same unified page doubles as a study view for answers and explanations, and completed results sync into practice records automatically. The limitation that follows is structural. Progress does not follow a person to a second machine, which is exactly the gap the self-hosted server branch with multi-device sync is built to close, and data backup is named in the feature list without the visible text saying where an export goes or what format it takes.
The hosting guidance is a list of paths that would 404
Static hosting gets one paragraph and it is mostly a warning. The runtime files can go on static hosting for personal or small scale use, and the full directory hierarchy has to be kept, because dropping any level produces 404s for bundles, question banks, fonts, images, PDFs, audio and generated assets. That list is also the practical map of the project: the fonts and images sit beside the question banks rather than in a build output directory, and the generated assets are runtime inputs, not artefacts you can regenerate after deploying. The same paragraph tells you to re-read the usage notice before any public deployment and makes the distinction the whole notice depends on: a page that can be deployed is not a license to distribute it. Combined with the browser requirement of a recent stable Chrome or Edge, that is the entire stated environment, and no other browser or version range is named anywhere in the file.
Editorial conclusion
This suits a learner who wants practice material they control on their own machine, and it is a poor fit for anyone planning to publish a question bank site or a paid community, which the usage notice rules out in as many words. Three things to check before you start. Match the release tag to the branch you care about, because `main` is the static edition, `feature/multi-device-easy-deploy` is the server edition with sync, and `IELTS-WRITING-FEAT` is a different product again, and the branch table leaves its Status and Maturity columns empty. Expect listening to be absent from any public package, because it ships behind `INCLUDE_LOCAL_LISTENING=1` and a hand placed index rather than in the download. And decide early whether browser local storage is acceptable, since that is why the multi-device branch exists and why progress does not follow you to another machine by default.
Frequently asked questions
How do I run the IELTS-practice reading app on my own machine?
Download and extract the full project, keep the directory structure intact instead of copying index.html alone, open index.html in a recent Chrome or Edge, and confirm the question list loads in Library. Practice pages open in a new window, so pop-ups must be allowed.
Does the public IELTS-practice release include listening audio and PDFs?
No. The public repository and the standard release packages leave out listening audio, question sources, PDFs, the full ListeningPractice directory and any pre-generated listening index. Missing files there are expected rather than a defect.
What license applies to IELTS-practice, and what does it not cover?
The code is governed by the LICENSE file and the repository records GPL-3.0. Question sources, articles, audio, PDFs and images stay with their original copyright holders and are recommended for personal study and exam preparation only.
How do I add my own listening material to IELTS-practice?
Place a generated index at assets/generated/listening-exams/manifest.js and listening-index.compat.js, keep to the P1 to P4 structure, and build with INCLUDE_LOCAL_LISTENING=1 to include your own ListeningPractice folder in a personal-use package.
Why does IELTS-practice maintain three branches?
main is the pure frontend static edition, feature/multi-device-easy-deploy is a self-hosted server edition with multi-device data sync, and IELTS-WRITING-FEAT is an AI-native client with AI writing scoring, reading coaching and self-evolution.
Official sources
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.
[](https://hysenlabs.com/projects/sallowayma-git-ielts-practice)Star history chart for your README
[](https://hysenlabs.com/projects/sallowayma-git-ielts-practice)Was this useful?