active 2026-07-04 → 2026-08-27 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 55 days from 2026-07-04 to 2026-08-27. Pushes: 4 total, peak 2 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 8 total, peak 4 in a day. Comments: 7 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| chonilius | 10 | 4 | 0 | 0 |
| drips-wave[bot] | 2 | 0 | 0 | 2 |
| grantfox-oss[bot] | 2 | 0 | 0 | 0 |
| OlaGreat | 1 | 0 | 0 | 1 |
| kolade000999 | 1 | 0 | 0 | 1 |
| N-otorious | 1 | 0 | 0 | 1 |
| Adewumi99 | 1 | 0 | 0 | 1 |
| Gabriel-teck | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue#9chonilius2026-08-27 14:41OAuth account-linking flow: verify passport-github2 strategy against account takeover via unverified/changed GitHub emails
- Issue comment#15Gabriel-teck2026-08-27 08:49Percentage-split validation for teams and split-releases can be gamed with more than 100 recipients or negative/NaN percentages bypassing sum checks
- Issue#53chonilius2026-08-27 08:19Bounty.issue uses onDelete: CASCADE unlike every other financial relation in the schema — deleting the linked Issue hard-deletes an in-flight, possibly-funded Bounty
- Issue comment#48kolade0009992026-08-27 07:46MaintenancePoolService.deposit creates a brand-new orphaned Escrow row on every deposit after the first, permanently stranding those funds outside assignReward's reach
- Issue comment#169OlaGreat2026-08-26 19:38apportionBasisPoints doesn't validate that its own input sums to ~100 before force-normalizing the output — and has no test for that scenario
- Issue comment#156drips-wave[bot]2026-08-26 19:11CI workflow only triggers on pull_request to main — a direct push bypasses the entire pipeline including the secret scan
- Issue comment#136N-otorious2026-08-26 08:26users.e2e-spec.ts's two "should reject unauthenticated requests with 401" tests both actually assert .expect(403)
- Issue comment#109drips-wave[bot]2026-08-25 20:12eslint downgrades @typescript-eslint/no-floating-promises and no-unsafe-argument from error to warn
- Issue comment#91Adewumi992026-08-25 17:55EscrowController.splitRelease returns raw Payment[] entities, bypassing the toPublicEscrow response shaping every other escrow endpoint uses
- Issue#95chonilius2026-08-21 21:24SorobanClientService has no dedicated spec file — the real invoke/poll/toScVal logic is never unit tested
- Issue#95chonilius2026-08-21 21:24SorobanClientService has no dedicated spec file — the real invoke/poll/toScVal logic is never unit tested
- Issue#177chonilius2026-08-21 21:10jest config doesn't separate DB-requiring integration specs from unit specs — npm run test fails without a live Postgres, with no clear signal why
- Issue#98chonilius2026-08-21 12:50JwtModule's expiresIn is cast via `as unknown as number`, masking a string/number type mismatch
- Issue#48grantfox-oss[bot]2026-08-16 01:00MaintenancePoolService.deposit creates a brand-new orphaned Escrow row on every deposit after the first, permanently stranding those funds outside assignReward's reach
- Issue#15grantfox-oss[bot]2026-07-15 22:24Percentage-split validation for teams and split-releases can be gamed with more than 100 recipients or negative/NaN percentages bypassing sum checks
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.