Compatibility layer of the EESSI project
active 2025-06-04 → 2026-07-31 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 423 days from 2025-06-04 to 2026-07-31. Pushes: 6 total, peak 2 in a day. Pull requests: 11 total, peak 2 in a day. Issues: 4 total, peak 1 in a day. Comments: 74 total, peak 9 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| bedroge | 43 | 2 | 2 | 36 |
| boegel | 18 | 1 | 4 | 8 |
| eessi-bot-aws[bot] | 16 | 0 | 0 | 16 |
| ocaisa | 9 | 2 | 2 | 4 |
| riscv-eessi-io-bot[bot] | 8 | 0 | 0 | 8 |
| casparvl | 7 | 0 | 1 | 2 |
| trz42 | 3 | 1 | 1 | 0 |
| xdelaruelle | 1 | 0 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#235eessi-bot-aws[bot]2026-05-29 05:16[WIP] Compatibility layer for EESSI version 2026.x
- Issue comment#235eessi-bot-aws[bot]2026-05-25 06:08[WIP] Compatibility layer for EESSI version 2026.x
- Issue comment#234ocaisa2026-04-11 07:28Users not found when password database is in a non-standard path
- Issue comment#234bedroge2026-04-10 13:49Users not found when password database is in a non-standard path
- Issue comment#234ocaisa2026-04-06 21:15Users not found when password database is in a non-standard path
- Issue comment#229boegel2026-02-03 16:43Add functionality for updating an existing compatibility layer
- Issue comment#229casparvl2026-02-03 16:34Add functionality for updating an existing compatibility layer
- Pull request#229casparvl2026-02-03 10:10
- Issue comment#229eessi-bot-aws[bot]2026-01-30 16:30Add functionality for updating an existing compatibility layer
- Issue comment#229eessi-bot-aws[bot]2026-01-30 15:39Add functionality for updating an existing compatibility layer
- Issue comment#229bedroge2026-01-30 15:38Add functionality for updating an existing compatibility layer
- Issue comment#229eessi-bot-aws[bot]2026-01-30 15:00Add functionality for updating an existing compatibility layer
- Issue comment#218bedroge2026-01-30 13:40Verify that user-defined-trusted-dirs paths are used by the dynamic loader
- Issue comment#229bedroge2026-01-29 19:24[WIP] Add functionality for updating an existing compatibility layer
- Issue comment#229riscv-eessi-io-bot[bot]2026-01-29 15:47[WIP] Add functionality for updating an existing compatibility layer
- Issue comment#229bedroge2026-01-29 15:47[WIP] Add functionality for updating an existing compatibility layer
- Issue comment#229riscv-eessi-io-bot[bot]2026-01-29 15:30[WIP] Add functionality for updating an existing compatibility layer
- Issue comment#229bedroge2026-01-29 14:19[WIP] Add functionality for updating an existing compatibility layer
- Issue comment#229bedroge2026-01-29 12:18[WIP] Add functionality for updating an existing compatibility layer
- Issue comment#232bedroge2025-12-02 10:48git & curl broken in EESSI 2025.06 compat layer?
- Issue comment#232casparvl2025-12-02 10:41git & curl broken in EESSI 2025.06 compat layer?
- Pull request#231xdelaruelle2025-11-08 16:40
- Issue comment#227eessi-bot-aws[bot]2025-09-16 12:27Update trusted directories for glibc to leverage variable symlinks
- Issue comment#227bedroge2025-09-16 12:27Update trusted directories for glibc to leverage variable symlinks
- Issue comment#227bedroge2025-09-16 12:26Update trusted directories for glibc to leverage variable symlinks
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.