08 — Current release register
Verification cutoff, stable versions, release dates, source links, and freshness defects for tracked context tools.
Summary
The release register fixes every comparison to a 2026-08-12 snapshot so superseded versions and stale benchmark claims cannot silently enter current verdicts. Authoritative dossier snapshot: 2026-08-12 UTC. “Latest” means the newest stable GitHub release visible at the cutoff, or newest tag when a project does not publish release objects. Adoption and activity fields come from GitHub's repository API. Stars are not an outcome metric.
Question and scope
Which exact stable releases and maintenance signals define the dossier’s current comparison set?
Method
The register queries release or tag metadata at the stated UTC cutoff, records the newest stable artifact and maintenance signals, and excludes stars from outcome judgments.
Findings
Core tools
| Tool | Current release | Published | Current adoption | Last repository push at cutoff | License today |
|---|---|---|---|---|---|
| Caveman | v2.0.0 | 2026-08-11 | 97,512★ / 240 subscribers / 5,622 forks | 2026-08-11 | MIT interfaces; BSL-1.1 engine-side components—see current licensing map |
| Headroom | v0.34.0 | 2026-08-05 | 65,972★ / 193 / 5,038 | 2026-08-11 | Apache-2.0 |
| RTK | v0.45.0 | 2026-08-07 | 75,756★ / 203 / 4,758 | 2026-08-10 | Apache-2.0 |
| lean-ctx | v3.9.18 | 2026-08-08 | 3,568★ / 22 / 323 | 2026-08-11 | Apache-2.0 |
API sources: Caveman, Headroom, RTK, lean-ctx.
Rising and adjacent tools
| Tool | Current release/tag | Current adoption | Created / active at cutoff | License/current boundary |
|---|---|---|---|---|
| pxpipe | v0.13.1, 2026-08-11 | 7,055★ / 25 subscribers / 610 forks | 2026-05-20 / 2026-08-11 | MIT |
| Context Mode | v1.0.169, 2026-06-29 | 19,802★ / 86 / 1,422 | 2026-02-23 / 2026-08-11 | Elastic License 2.0; source-available, not OSI open source |
| Paritok | tag v1.3.3; no GitHub release object | 1,031★ / 78 / 118 | 2026-07-15 / 2026-08-11 | Apache-2.0 repository; base model has its own license |
| jCodeMunch MCP | v1.108.271, 2026-08-10 | 2,542★ / 19 / 349 | 2026-02-09 / 2026-08-11 | GitHub API reports no SPDX identifier; inspect repository terms before embedding |
| Serena | v1.7.0, 2026-08-09 | 27,874★ / 86 / 1,851 | 2025-03-23 / 2026-08-10 | MIT |
| fff | v0.10.3, 2026-08-07 | 9,949★ / 20 / 412 | 2025-07-31 / 2026-08-11 | MIT |
| codedb | v0.2.5838, 2026-08-05 | 1,357★ / 9 / 79 | 2026-03-03 / 2026-08-05 | BSD-3-Clause |
| sem | v0.21.0, 2026-07-10 | 3,294★ / 6 / 98 | 2026-02-05 / 2026-07-18 | Apache-2.0 API metadata; repository also documents dual-license surfaces |
| mq | v0.8.2, 2026-08-10 | 1,005★ / 2 / 21 | 2025-02-24 / 2026-08-11 | MIT |
| Entroly | no tagged stable release | 435★ / 6 / 69 | 2026-03-07 / 2026-08-11 | Apache-2.0 |
| claude-context | no tagged release | 12,384★ / 57 / 910 | 2025-06-06 / 2026-07-14 | MIT |
| Repomix | v1.18.0, 2026-08-08 | 27,776★ / 70 / 1,483 | 2024-07-13 / 2026-08-11 | MIT |
API sources: pxpipe, Context Mode, Paritok, jCodeMunch, Serena, fff, codedb, sem, mq, Entroly, claude-context, Repomix.
Update rule
Future edits replace this snapshot; they do not append a release history. A changed stable version requires re-reading the release, current architecture, license, install/telemetry behavior, and evidence before carrying any verdict forward.
Implications for jackin❯
For jackin❯, the current release register evidence determines whether the mechanism is suitable for reuse, comparison, or rejection.
Limitations and unknowns
Freshness defects found in current upstream docs
- RTK's current README verification example names an older version than v0.45.0.
- RTK's current privacy and disclaimer documents disagree about telemetry default.
- Headroom's current
SECURITY.mdlabels an older release as latest. - lean-ctx v3.9.18 release notes contain a self-comparison changelog link.
- Paritok publishes current tags but no GitHub release objects.
These defects do not change the release metadata above. They lower confidence in unaudited prose and justify linking exact release artifacts.
Sources
Evidence and repository references are cited inline beside the claims they support.