Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Cumulative recorded downloads · since 2025-10-26
Across 18 known packages in repositories dahlia owns. Cumulative totals include recorded downloads before the selected range. Missing observations leave gaps; totals may be incomplete.
Top repositories
dahlia’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside dahlia’s account where dahlia opened or reviewed pull requests in the past 365 days.
Who noticed dahlia
Everyone who starred or forked dahlia’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories dahlia owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Fair enough, and I realize it's easy to ask for this from the outside. I didn't mean that I should be the one to do it, though, and I'm not sure I could. The fixes are public once the advisories go out, so anyone can backport them. But a signed and notarized build, an auto-update, a version number that scanners and distro trackers recognize: those only come from the project itself. A patched fork wouldn't reach most users. I maintain a few much smaller projects ([Fedify] and [LogTape], for instance) and try to ship patch releases for older minors, so I do have some sense of what it costs. It's far more manageable at that scale. I'd guess Ghostty's situation is harder, with more platforms, more packaging, and many more users. Please read my comment as a wish rather than a criticism of how the team spends its time. [Fedify]: github.com/fedify-dev/fedify/releases [LogTape]: github.com/dahlia/logtape/blob/main/CHANGES.md
Gukhanmun 0.3.0이 나왔습니다. 이제 신자체·간체도 사전과 대조해 읽고, 출력 한자의 자형도 고를 수 있습니다. 사전이 여러 읽기 후보를 갖게 됐고, 뒤따르는 조사에 따라 읽기가 정해집니다. 구두점 프로파일 옵션이 추가됐고, 외래어 표기 용례도 사전으로 넣었습니다. gukhanmun#32
Gukhanmun 0.3.0 is out. Hanja in shinjitai or simplified form now resolves against the dictionary, and output can switch registers. A Korean particle picks among retained readings. Punctuation profiles are opt-in; NIKL loanwords are bundled. gukhanmun#32
Gukhanmun 0.3.0 is out. Hanja in shinjitai or simplified form now resolves against the dictionary, and output can switch registers. A Korean particle picks among retained readings. Punctuation profiles are opt-in; NIKL loanwords are bundled.
Gukhanmun 0.3.0이 나왔습니다. 新字體나 簡體字로 적힌 漢字도 辭典과 對照해 읽고, 出力할 때는 字體를 바꿀 수 있습니다. 辭典이 讀音 候補를 남기므로 뒤따르는 助詞에 따라 그 中 하나를 고릅니다. 句讀 符號 프로파일 옵션이 追加되었고, 國立國語院 《外來語 表記 用例》가 辭典으로 包含되었습니다. v0.2.x에서 올리면 ko-kr 프리셋 出力이 달라지고 辭典 形式도 v2로 바뀌었습니다.