Each resource carries its own ownership record as ordinary cloud tags. AWS can tell you what an estate contains, and your IAM already decides who may read or change it. Nothing else to permission, and no lock to manage. Experimental, AWS only.
active 2026-08-12 → 2026-10-22 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 72 days from 2026-08-12 to 2026-10-22. Pushes: 175 total, peak 25 in a day. Pull requests: 120 total, peak 35 in a day. Issues: 222 total, peak 62 in a day. Comments: 62 total, peak 18 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 |
|---|---|---|---|---|
| lex00 | 575 | 173 | 119 | 61 |
| github-actions[bot] | 4 | 2 | 1 | 1 |
Recent activity
Latest issues, pull requests and releases
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.