Skip to content

active 2025-01-022026-07-17 (UTC)

Partial coverage12,492 / 14,201 hourly files (88%) · 2 absent upstream · 1,703 failed, retryable2024-12-272026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
205
Pushes
122
Pull requests
12
Issues
44
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 562 days from 2025-01-02 to 2026-07-17. Pushes: 122 total, peak 6 in a day. Pull requests: 12 total, peak 2 in a day. Issues: 44 total, peak 5 in a day. Comments: 25 total, peak 3 in a day. Stars: 0 total, peak 0 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
Frontear2061221225

Recent activity

Latest issues, pull requests and releases

  • Pull request#73Frontear2026-03-26 03:47
  • Pull request#72Frontear2026-02-22 03:35
  • Pull request#71Frontear2025-12-28 22:58
  • Issue#66Frontear2025-12-01 02:45
    Migrate from auto-cpufreq to TuneD or power-profiles-daemon
  • Issue#29Frontear2025-11-18 01:56
    Abstract hardware details into a `my.hardware` namespace
  • Pull request#69Frontear2025-11-10 23:52
  • Issue#65Frontear2025-10-26 03:59
    Investigate performance issues in GNOME
  • Issue#65Frontear2025-10-26 03:59
    Investigate performance issues in GNOME
  • Issue#65Frontear2025-10-26 03:59
    Investigate performance issues in GNOME
  • Issue#64Frontear2025-10-26 01:02
    Create a new type that prohibits paths constructed via string interpolation
  • Issue comment#64Frontear2025-10-26 01:02
    Create a new type that prohibits paths constructed via string interpolation
  • Issue#64Frontear2025-10-26 00:57
    Create a new type that prohibits paths constructed via string interpolation
  • Issue comment#63Frontear2025-10-25 05:29
    UX issues with swaylock and fprintd authentication
  • Issue comment#63Frontear2025-10-19 21:32
    UX issues with swaylock and fprintd authentication
  • Issue comment#63Frontear2025-10-19 20:44
    UX issues with swaylock and fprintd authentication
  • Issue#63Frontear2025-10-19 20:43
    UX issues with swaylock and fprintd authentication
  • Issue#63Frontear2025-10-19 20:43
    UX issues with swaylock and fprintd authentication
  • Issue#63Frontear2025-10-19 20:43
    UX issues with swaylock and fprintd authentication
  • Issue#62Frontear2025-10-19 20:16
    Support using a fingerprint for keyring decryption at login
  • Issue#62Frontear2025-10-19 20:16
    Support using a fingerprint for keyring decryption at login
  • Issue#38Frontear2025-10-17 05:21
    Prefer to wrap configuration files into the application via CLI arguments instead of linking into `$HOME`
  • Issue comment#38Frontear2025-10-17 05:21
    Prefer to wrap configuration files into the application via CLI arguments instead of linking into `$HOME`
  • Issue comment#31Frontear2025-10-04 04:54
    Remove excessive modularization and open-ness from the current modules through a world refactor
  • Issue#31Frontear2025-10-04 04:54
    Remove excessive modularization and open-ness from the current modules through a world refactor
  • Issue comment#56Frontear2025-09-29 03:59
    Check the configuration of `security.pam.services.swaylock` and see if it's sufficient

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