Kratos: a theme skeleton, two duplicate tracker links, and three 4.3.x releases
WordPress theme that focus on reading experience
At a glance
- What is it?
- seatonjiang/kratos is a PHP WordPress theme with a 174 word README that installs by telling you to upload a zip, a header whose bug and feature links resolve to the same URL, a licence label that disagrees with its own filename, and a release history of three patch bumps on one minor line.
- Who is it for?
- Use it if you want a single column reading focused WordPress theme with a deliberately small template set and are happy to install it from a zip, since that absence of archive, sidebar and search form templates looks chosen rather than unfinished.
- 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 last received commits 126 days ago.
- What is it written in?
- Mainly PHP, 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
- seatonjiang/kratos3,319 ★ · -7
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| seatonjiang/kratos | 3.3k | 3.3k |
-7 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The header offers a bug link and a feature link and both resolve to the same URL
Below the language switcher, the README puts a Report Bug link and a Request Feature link on one line, separated by a middle dot. Both of them point at github.com/seatonjiang/kratos/issues. The same URL, twice, under two different labels.
That is not unusual on small projects, where a single tracker serves both purposes. What makes it worth naming is that the header also contains three bare anchor tags immediately above, and those three do have distinct targets: the issues page, the pull requests page, and the licence file on main. So the document has six links to the tracker area, three empty ones pointing at three different places and two labelled ones pointing at one.
The three empty anchors are the other half. Each one contains nothing but whitespace between its opening and closing tags, so they render as nothing at all. They are the remains of what were probably three badges, and whatever images they pointed at are not present in the file.
None of this is a functional problem. A reader who wants to report a bug gets to the tracker, which is what they wanted. It is a first-impression problem on a repository with 3327 stars, where the visual header of the front page is two paragraphs of empty markup plus a duplicated link.
The licence link reads LICENCE and the file it points at is LICENSE
The licence section names the GNU General Public License v3.0 and then links to the file for details. The link text is LICENCE, with the c. The URL it points at ends in LICENSE, without the c. And the file in the repository's top level is named LICENSE, without the c.
So the label and the target disagree with each other, and the target is the correct one. The URL works; only the visible word is wrong. It is a one character slip in the one place on the page where precision matters most, because this is the line someone building a compliance checklist reads.
The section also calls it the project rather than the theme, in a sentence saying the project is released under those terms. Small thing, but the repository is a WordPress theme and the language does not match the repository description, which is a theme that focuses on reading experience.
The good news is that the licence itself is unambiguous where it counts. The tree carries both LICENSE and CODE_OF_CONDUCT.md at the top level, the repository is detected as GPL-3.0, and the README states the same version the file does. One wrong letter in a link label is the only discrepancy.
Quick start is five clicks through the theme uploader and its first sentence does not parse
The installation section is five numbered steps and every one of them is a click inside the WordPress administration area. Download the zip, go to Appearance and Themes, click Add New, use the Upload Theme option, choose the file, install, then activate from the catalog.
The first step is where the prose breaks down. It says to download the theme's .zip file from the source file to your local computer. There is no thing called the source file. What is meant is the source, or the release, and either way the instruction as written points at something that does not exist, on the very step that starts the process.
Steps 2 and 5 also name the same screen two different ways. Step 2 says to head to Appearance and Themes. Step 5 says to select the Appearance tab, then open the theme catalog. Theme catalog is the WordPress term for the same screen.
More significant is what the section never mentions. There is no minimum WordPress version, no minimum PHP version, no list of required plugins, no note about which page builder or editor it is built for, and no mention of what the theme actually changes once activated. For a theme whose entire stated purpose is a focus on reading experience, the readme tells you how to upload a file and nothing about what you get.
The tree ships the required templates and no archive, sidebar or search form
The top level of this repository is a complete WordPress theme skeleton, which is worth reading as a list rather than skipping past. There is index.php, header.php, footer.php, single.php, page.php, a second page template called page-full.php, 404.php, comments.php and functions.php. Alongside them are style.css, which is where a theme declares its name and version to WordPress, and screenshot.png, which is what makes the theme appear with a preview image in the catalog.
Then there are the absences, and for a theme they are informative. There is no archive.php. WordPress falls back to index.php for category, tag, author and date views, so those pages exist but share the front page's template. There is no sidebar template and no sidebar in the listing, so a single-column layout is the deliberate shape rather than a default. There is no search form template, so the search widget renders with whatever WordPress provides.
Two include directories sit alongside the templates, inc/ and pages/, plus an assets/ directory that has to carry prebuilt CSS and JavaScript since there is no build configuration in the repository to produce them.
There is also a translation path: a languages/ directory and a crowdin.yml at the top level, alongside the Chinese README. Three people are maintaining those three moving parts, and only the crowdin file says how the strings reach them.
Three ignore files describe a linting toolchain the repository never declares
The listing opens with .eslintignore and .prettierignore, sitting next to .gitignore. That is three ignore files for three tools, and two of those tools are JavaScript linters and formatters.
There is no configuration for either one. No ESLint config file appears in the top level, no Prettier config appears, and there is no package.json, no lockfile and no node_modules instruction anywhere in the listing. So the repository carries two ignore files whose entire content is a list of paths to skip, without saying which rules are being applied to the paths that are not skipped, and without declaring the tool versions.
The same is true of the PHP side. functions.php, header.php, footer.php, single.php, page.php, page-full.php, 404.php and comments.php are eight PHP files at the top level, and nothing in the listing declares a PHP standard, a static analysis tool or a test runner for them.
The absence of package.json is consistent with the theme shipping as source rather than as a build artifact. There is no compile step, so assets/ holds what the theme actually loads. But the ignore files are the residue of a different workflow, one where a formatter was run over the tree at some point, and they are the only evidence of it. A contributor cloning the repository has no way to reproduce whatever those tools enforced.
A Contributing section, a code of conduct, and no contributing guide
The README has a Contributing section two sentences long. It welcomes contributions and says they can be submitted as pull requests or as issues, and closes with have a good time.
The repository has a CODE_OF_CONDUCT.md at the top level and does not have a contributing file of any name. So the one section of the README devoted to participation describes a process that is documented nowhere, while the document that does exist to govern behaviour is not linked from the page.
That is the asymmetry worth noticing. A code of conduct is the file you most want to be findable from the front page, because it is the one people read before deciding whether a space is for them. It is present and unreferenced. A contributing guide is the file you most want to be findable if you intend contributors, and it is absent entirely, with the README's two sentences standing in for it.
The README does do one thing well here, which is naming both routes. Pull requests and issues are both accepted, and the header above links to both, even if the two labelled links share a URL. With 24 open issues and 596 forks against 3327 stars, the fork ratio suggests people are installing rather than contributing, so the missing guide is doing less damage than it might elsewhere.
All three releases on record are 4.3.x patch bumps, and the last commit is the last release
The release history on record is three entries. v4.3.2 on 2025-02-08, v4.3.3 on 2025-11-17, and v4.3.4 on 2026-07-12.
Two things stand out. First, all three are patch bumps on the same 4.3 line. There is no 4.2 and no 4.4 in what is visible, so over the span these three releases cover the minor version has not moved at all, which for a theme means eighteen months without a feature release that anyone can name from the tags.
Second, the spacing. Nine months between the first two and about eight between the second and third. That is roughly two releases a year, on a project whose last commit was 2026-07-12.
The last push timestamp is 2026-07-12T08:17:00Z and the v4.3.4 release timestamp is 2026-07-12T08:17:00Z. They are identical to the second. That means the tip of the default branch is exactly the v4.3.4 release commit, with no work committed after it, which is the cleanest possible state for anyone who wants to reason about which code they are running.
It also means the gap between now and the last change is about three months, which is unremarkable for a theme rather than alarming. Worth stating plainly rather than dressing up: the repository is not archived, and it has had no commit since the release that is currently the newest tag.
Editorial conclusion
Use it if you want a single column reading focused WordPress theme with a deliberately small template set and are happy to install it from a zip, since that absence of archive, sidebar and search form templates looks chosen rather than unfinished. Two things to check before you rely on it: the README states no WordPress or PHP version requirement and no plugin requirement, so test on a staging site first, and note that the last commit is the v4.3.4 release commit with nothing after it. Skip it if you need documented upgrade guidance or a contributing process, because there is no contributing file and no upgrade section.
Frequently asked questions
How do I install the Kratos WordPress theme?
Download the theme zip, then in WordPress go to Appearance > Themes, click Add New, use the Upload Theme option, choose the file and click Install Now, then activate it from the theme catalog. The README states no minimum WordPress version, no PHP version and no required plugins.
Does the Kratos README link to a separate feature request page?
No. The header carries a Report Bug link and a Request Feature link, and both point at the same github.com/seatonjiang/kratos/issues URL. Three bare anchors above them point at the issues page, the pull requests page and the licence file, and render as empty markup.
Is the Kratos licence file named LICENCE or LICENSE?
LICENSE. The README's link text reads LICENCE with a c, while both the URL it points at and the file in the repository are named LICENSE. The theme is released under the GNU General Public License v3.0.
What templates does the Kratos theme ship?
index.php, header.php, footer.php, single.php, page.php, page-full.php, 404.php, comments.php and functions.php, with style.css and screenshot.png alongside them, plus inc/, pages/, assets/ and languages/ directories. There is no archive.php, no sidebar template and no search form template.
How often is the Kratos theme released?
The three releases on record are v4.3.4 on 2026-07-12, v4.3.3 on 2025-11-17 and v4.3.2 on 2025-02-08. All three are patch bumps on the same 4.3 line, and the last commit to main carries the same timestamp as v4.3.4.
Does the Kratos theme have a contributing guide?
No contributing file exists in the repository. The README has a two sentence Contributing section inviting pull requests and issues, and the tree carries a CODE_OF_CONDUCT.md that the README never links.
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/seatonjiang-kratos)Star history chart for your README
[](https://hysenlabs.com/projects/seatonjiang-kratos)Was this useful?