Skip to content

Splinter is a minimalist, high-speed, lock-free message bus and pub/sub KV store that uses shared memory (memfd) or, optional memory-mapped files for persistent backing. Designed specifically for local LLM workloads and their sanitation needs, but versatile enough to scale to 300k ops/sec on an i3.

active 2025-08-012026-01-12 (UTC)

Partial coverage13,889 / 16,606 hourly files (84%) · 2 absent upstream · 2,717 failed, retryable2024-09-182026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
230
Pushes
182
Pull requests
2
Issues
22
Stars
3
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 165 days from 2025-08-01 to 2026-01-12. Pushes: 182 total, peak 12 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 22 total, peak 10 in a day. Comments: 6 total, peak 2 in a day. Stars: 3 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
timthepost21218226

Recent activity

Latest issues, pull requests and releases

  • Releasetimthepost2026-01-10 18:00
    Version 0.9.1 - Bugfix Release
  • Releasetimthepost2026-01-09 02:56
    Version 0.9.0 - Almost There!
  • Issue#8timthepost2026-01-05 20:40
    Implement 'shard' to synchronize splinter watches with underlying file system events
  • Issue#8timthepost2026-01-05 20:40
    Implement 'shard' to synchronize splinter watches with underlying file system events
  • Issue#14timthepost2026-01-05 20:39
    Implement callbacks to give 'shards' more functionality
  • Issue#14timthepost2026-01-05 20:39
    Implement callbacks to give 'shards' more functionality
  • Issue#14timthepost2026-01-05 20:39
    Implement callbacks to give 'shards' more functionality
  • Issue#14timthepost2026-01-05 20:39
    Implement callbacks to give 'shards' more functionality
  • Issue#13timthepost2026-01-05 20:34
    Implement vector storage and lazy sidecar vector computation
  • Issue#13timthepost2026-01-05 20:34
    Implement vector storage and lazy sidecar vector computation
  • Issue#13timthepost2026-01-05 20:34
    Implement vector storage and lazy sidecar vector computation
  • Issue#13timthepost2026-01-05 20:34
    Implement vector storage and lazy sidecar vector computation
  • Issue#8timthepost2026-01-01 00:46
    Implement 'shard' to synchronize splinter watches with underlying file system events
  • Issue#8timthepost2026-01-01 00:46
    Implement 'shard' to synchronize splinter watches with underlying file system events
  • Issue comment#8timthepost2025-12-31 13:43
    Implement 'shard' to synchronize splinter watches with file system events
  • Releasetimthepost2025-12-30 14:58
    Version 0.5.5 - Recurring Maintenance Release
  • Issue comment#6timthepost2025-12-30 02:22
    Don't auto vacuum / auto scrub dirty pages
  • Issue#4timthepost2025-12-30 00:17
    Make persistent mode a first-class feature
  • Issue comment#4timthepost2025-12-30 00:17
    Make persistent mode a first-class feature
  • Pull request#12timthepost2025-12-28 23:23
  • Pull request#11timthepost2025-12-23 18:19
  • Releasetimthepost2025-12-17 01:31
    Version 0.5.3 - One tool to rule them all.
  • Issue#7timthepost2025-10-07 17:59
    (Possibly) Support INCR/DCR/MATH based entirely on slot epoch
  • Issue#6timthepost2025-10-07 16:40
    Don't auto vacuum / auto scrub dirty pages
  • Issue#5timthepost2025-10-06 16:21
    Version 0.5.0

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 3 stars here means stars gained during the window, not the repo's star count.