A repository for storing public tasks
active 2024-06-27 → 2026-03-12 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 624 days from 2024-06-27 to 2026-03-12. Pushes: 1 total, peak 1 in a day. Pull requests: 3 total, peak 1 in a day. Issues: 56 total, peak 28 in a day. Comments: 20 total, peak 4 in a day. Stars: 1 total, peak 1 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 |
|---|---|---|---|---|
| MantisClone | 65 | 1 | 3 | 7 |
| coderabbitai[bot] | 10 | 0 | 0 | 7 |
| tristanwallaert-netizen | 4 | 0 | 0 | 3 |
| greptile-apps[bot] | 3 | 0 | 0 | 2 |
| aimensahnoun | 2 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue#178MantisClone2026-03-12 21:17Request API - Evaluate whether staging/CI should use separate RPC endpoints from production
- Issue#174MantisClone2026-03-05 18:08Portal - Remove deployment infrastructure
- Issue#171tristanwallaert-netizen2026-03-04 22:31[Or.0.1] As am orchestrator, I should be able to connect to Request Network API via a client ID and subscribe to a webhook to listen to a given destination's request
- Issue#164MantisClone2026-03-03 13:26BlockScout - Create integration guide (Notion page)
- Issue#164MantisClone2026-02-27 22:38BlockScout - Create integration guide (Notion page)
- Issue comment#92MantisClone2026-02-24 22:49[Py.2.3] As a Payee, I should be able to create a one-off request to get paid via an orchestrator, by granting an orchestrator the right to create requests on my behalf by creating API keys under a set payment destination
- Issue comment#91MantisClone2026-02-24 22:41[Py.2.2] As a Payee, I should be able to create a one-off request to get paid via a Front-end
- Issue comment#158tristanwallaert-netizen2026-02-22 13:21[Py.10.1] As a Payee, I should be able to store safely spececific information linked to my payments without even RN being able to access this data
- Issue comment#72tristanwallaert-netizen2026-02-11 11:46[Pr.2.1.a] As a payer, I should be able to pay one or multiple request safely - via a self hosted (IPFS) front end preventing contract spoofing for same chain transaction
- Issue#156MantisClone2026-02-06 05:12[Py.1.1.d] As a Payee, I should be able to choose who bears the fee (recipient or sender)
- Issue#151MantisClone2026-01-21 18:21chore: Remove pull_request trigger from auto-project workflows
- Issue#151MantisClone2026-01-21 18:19[Chore] Remove pull_request trigger from auto-project workflows
- Pull request#150MantisClone2026-01-21 17:40
- Issue#145MantisClone2026-01-21 04:37Secure Payment Page - Developer Integration Guide
- Issue comment#79tristanwallaert-netizen2026-01-20 17:45[Pr.2.4.c] As a payer, I should be able to pay one or multiple request from every chain - as same chain on Top 2 non EVMs in used stablecoin addresses - Starting by Tron
- Pull request#132MantisClone2026-01-20 06:30
- Issue#140MantisClone2026-01-20 06:08IPFS Release - Complete first official release
- Issue comment#133coderabbitai[bot]2026-01-19 21:04[Pr.1.0.a] As a payer, I should be able to create a one-off request to pay someone via the SDK
- Issue#137MantisClone2026-01-19 21:04[Py.1.1.b] As a Payee, I should be able to set my payment preferences via a Front-end - by choosing between using a unique smart contract for each consumer or a unique Smart contract
- Issue#135MantisClone2026-01-19 21:04[Pr.1.3.a] As a payer, I should be able to create a one-off request to pay someone via an orchestrator
- Issue comment#132coderabbitai[bot]2026-01-19 20:53chore: add reopen-issue-if-prs-open workflow
- Issue#131MantisClone2026-01-19 19:16[Automation] - Issues close prematurely when first PR in a stack merges
- Issue comment#131coderabbitai[bot]2026-01-19 18:22[Automation] - Issues close prematurely when first PR in a stack merges
- Issue#131MantisClone2026-01-19 18:22[Automation] - Issues close prematurely when first PR in a stack merges
- Issue#130MantisClone2026-01-17 20:23Chore - Deploy auto-project workflow to all tracked repos
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.