Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Cumulative recorded downloads · since 2025-10-20
Across 5 known packages in repositories benbjohnson owns. Cumulative totals include recorded downloads before the selected range. Missing observations leave gaps; totals may be incomplete.
Top repositories
benbjohnson’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside benbjohnson’s account where benbjohnson opened or reviewed pull requests in the past 365 days.
Who noticed benbjohnson
Everyone who starred or forked benbjohnson’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.
- Gold
- 01st place finishes
- Silver
- 02nd place finishes
- Bronze
- 13rd place finishes
- Awarded repositories
- 1Owned by benbjohnson now
Repositories
Ordered by gold, then silver, then bronze.
- litestreamBest: 3rd by stars, 452 stars001
Every award
Top-three finishes of these repositories in completed trending days and weeks, newest first.
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
@rachelnabors With this extension wind-action: x.com I using a redaction pipeline, litestream, and Jev: benbjohnson/litestream
Litestream: Streaming replication for SQLite (15k stars) What it does All text below is quoted directly from the project README. >Streaming replication for SQLite. Litestream: - Litestream is a standalone disaster recovery tool for SQLite. - It runs as a background process and safely replicates changes incrementally to another file or S3. - Litestream only communicates with SQLite through the SQLite API so it will not corrupt your database. Source database changes: - When Litestream begins replicating a database, it creates an internal _litestream_lock table in the source SQLite database. - This is expected and safe to leave in place. - Litestream uses the table to acquire SQLite's write lock while coordinating synchronization around WAL checkpoints. - Restarting Litestream recreates the missing table automatically. Repository benbjohnson/litestream Repository stats |Metric|Value| |:-|:-| |Stars|14,539| |Forks|448| |Last release|v0.5.17 (2026-08-31)| |Languages|Go 71.4%, C 22.4%, Shell 5.8%| |Contributors|48| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|None| |AI co-authored commits|Claude: 216, Copilot: 1| Main contributor |Field|Value| |:-|:-| |Name|Ben Johnson| |GitHub|@benbjohnson| |Commits to this repo|368 (top contributor)| |Company / Location|Fly.io / Colorado| |X / Twitter|@benbjohnson| |Followers|4.3k| ────────────────────────────── 📌 How many great GitHub repos have you discovered and completely forgotten about? Don't let another useful tool disappear into your Reddit feed. Get the community's best repos, organized by category, plus key takeaways from real developer discussions, delivered to your inbox twice a week. 📬 Never lose track of great repos again. Subscribe free.
Litestream streams SQLite changes to S3 or any object storage as they happen, so a single-server app gets point-in-time restore without moving to Postgres. 14.5K stars, still actively maintained. benbjohnson/litestream
Litestream: Streaming Replication for SQLite
I ran into a similar thing with our metrics at work, funnily enough. Except for us, it was the metrics scrape holding a read lock scripts several (possibly slow) collectors while metrics updates required the write lock. I ended up replacing it with an atomic pointer to some immutable collections, so we effectively did snapshot reads.