Skip to content

krish567366/submicro-execution-engine

View on GitHub ↗Related repositories →

Sub-microsecond bare-metal execution engine with deterministic replay, lock-free order path, and hardware-timestamped latency measurement.

active 2025-12-152026-05-07 (UTC)

Partial coverage11,687 / 12,918 hourly files (90%) · 2 absent upstream · 1,228 failed, retryable2025-02-182026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
103
Pushes
37
Pull requests
0
Issues
3
Stars
50
Forks
9

Activity over time

Daily event counts in the loaded window

Line chart, 144 days from 2025-12-15 to 2026-05-07. Pushes: 37 total, peak 10 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 3 total, peak 3 in a day. Comments: 1 total, peak 1 in a day. Stars: 50 total, peak 29 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
krish567366403701
doobidoo1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#1krish5673662025-12-27 17:28
    Code does not compile - Multiple bugs prevent building
  • Issue#1krish5673662025-12-27 16:24
    Code does not compile - Multiple bugs prevent building
  • Issue#1krish5673662025-12-27 16:24
    Code does not compile - Multiple bugs prevent building
  • Issue#1doobidoo2025-12-27 13:59
    Code does not compile - Multiple bugs prevent building

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