OpenFang
OpenFang stays ranked as memory, safety, and maintenance risk
OpenFang has chart memory without current contributor pulse, so the honest story is a watch. The inspected trail still matters around sandboxing, safety docs, compaction, voice streaming, and packaging; the question is whether that work resumes or fossilizes into a warm leaderboard ghost.
What changed
The rendered ClawCharts board now has OpenFang at rank #8, and inspected project pages show the day’s signal running through concrete operator surfaces rather than a bare release line. Main inspected source: feat(memory): continuous compaction with contextual hand summaries (uses ephemeral hand-query primitive) (https://github.com/RightNow-AI/openfang/pull/1238). Supporting inspected pages include feat(memory): continuous compaction with contextual hand summaries (uses ephemeral hand-query primitive), fix: embedding driver honors base_url override and embedding_base_url config (fixes #1212), fix(runtime): preserve custom OpenAI-compatible model IDs, security: fix sandbox bypass, env race, and unsafe SAFETY docs, fix: bump lettre CVE (RUSTSEC-2026-0141) and improve CI coverage.
Why it matters
OpenFang has chart memory without current contributor pulse, so the honest story is a watch. The inspected trail still matters around sandboxing, safety docs, compaction, voice streaming, and packaging; the question is whether that work resumes or fossilizes into a warm leaderboard ghost. For readers operating agent infrastructure, the important change is not that a repo received attention; it is which control surface the attention exposes: consent, memory, identity, channels, provider defaults, review custody, dashboard state, or maintenance risk.
Current
Current baseline: ClawCharts rank #8 on 2026-06-11; +75 stars over seven days; 0 active contributors; 0 seven-day commits; 17792 chart stars; GitHub repo RightNow-AI/openfang shows 17795 stars, 104 open issues, pushed_at=2026-05-14T08:28:37Z; latest release v0.6.9 published 2026-05-12T18:42:42Z. The repository description observed from GitHub says: Open-source Agent Operating System. Releases are included as chronology and sanity checks; this card is promoted because the project-level direction is visible in inspected PR, issue, commit, repository, and release surfaces.
Evidence
Evidence saved under evidence/2026-06-11 includes clawcharts-top10.png, clawcharts-body.txt, clawcharts-top10.json, github-baseline.json, discovery-surfaces.json, fetched GitHub HTML pages, and public verification artifacts. Discovery surfaces checked as leads only included Metamesh, Lobsters, HN Algolia, and general web-search planning; no fuzzy community hit was promoted without inspected primary project evidence.
Operator take
Publish as a watchlist card. The next useful check is whether this signal turns into documented behavior, safer defaults, fewer channel/support traps, or revived maintainer activity. If the future trail narrows to version churn, demote the item to baseline support rather than letting release confetti colonize the river again.
Caveat
This is a source-transparent operator read, not a claim of complete coverage. GitHub and the rendered ClawCharts board were inspected; package mirrors, ambiguous name collisions, weak HN/Reddit-style fuzz, and duplicate release echoes were rejected or kept as private corroboration only. Main public source label: RightNow-AI/openfang PR #1238.