active 2026-03-21 → 2026-08-08 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 141 days from 2026-03-21 to 2026-08-08. Pushes: 13 total, peak 8 in a day. Pull requests: 9 total, peak 5 in a day. Issues: 9 total, peak 4 in a day. Comments: 16 total, peak 7 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
Recent activity
Latest issues, pull requests and releases
- Issue comment#25konard2026-04-20 23:29Sync pjson with repo-guard governance trust model
- Issue comment#25konard2026-04-20 23:27Sync pjson with repo-guard governance trust model
- Issue comment#24konard2026-04-20 23:26# Issue: Синхронизировать pjson с последними governance/trust-model изменениями repo-guard
- Issue#19netkeep802026-04-19 22:43# Issue 012 — Add requirements-strict profile and migrate pjson to it
- Pull request#23konard2026-04-19 22:43
- Issue comment#23konard2026-04-19 22:38Migrate pjson to requirements-strict policy
- Pull request#23konard2026-04-19 22:25
- Issue comment#22konard2026-04-19 22:21Migrate docs heading checks to repo-guard
- Pull request#22konard2026-04-19 22:10
- Issue#17netkeep802026-04-19 22:09# Issue 010 — Integrate repo-guard into pjson PR workflow
- Pull request#21konard2026-04-19 22:09
- Issue comment#20konard2026-04-19 21:37Добавить pilot policy repo-guard для трассировки требований
- Pull request#20konard2026-04-19 21:15
- Issue#17netkeep802026-04-19 19:31# Issue 010 — Integrate repo-guard into pjson PR workflow
- Issue#16netkeep802026-04-19 19:30# Issue 009 — Create pjson pilot repo-guard policy for requirements-aware control
- Issue comment#14konard2026-03-22 09:29Описание понятия леса AVL-деревьев: декомпозиция на требования
- Issue comment#14konard2026-03-22 09:28Описание понятия леса AVL-деревьев: декомпозиция на требования
- Issue#11netkeep802026-03-22 09:13Новое требование
- Issue comment#12konard2026-03-22 08:40Унификация типа AVL-дерева и типа JSON-узла: pptr как динамический тип
- Issue#11netkeep802026-03-22 08:29Новое требование
- Issue comment#10konard2026-03-22 08:18Трассировка требований pmm и валидация заголовков документации
- Pull request#8konard2026-03-22 07:19
- Issue comment#8konard2026-03-22 07:17Уточнить валидацию требований: трассировка, именование, содержание каталогов
- Pull request#8konard2026-03-22 07:12
- Issue#5netkeep802026-03-22 06:56Размышления про архитектуру
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.