Repository for "The Idempotency-Key HTTP Header Field"
active 2023-09-27 → 2025-03-24 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 545 days from 2023-09-27 to 2025-03-24. Pushes: 12 total, peak 2 in a day. Pull requests: 14 total, peak 5 in a day. Issues: 19 total, peak 3 in a day. Comments: 128 total, peak 14 in a day. Stars: 8 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 |
|---|---|---|---|---|
| jmileham | 53 | 0 | 0 | 48 |
| sdatspun2 | 35 | 8 | 8 | 12 |
| richsalz | 17 | 0 | 0 | 14 |
| awwright | 17 | 0 | 0 | 17 |
| asbjornu | 13 | 0 | 0 | 13 |
| darrelmiller | 12 | 0 | 0 | 5 |
| mnot | 5 | 0 | 1 | 3 |
| Acconut | 4 | 0 | 0 | 4 |
| jayadeba | 4 | 0 | 0 | 4 |
| github-actions[bot] | 4 | 4 | 0 | 0 |
| DavidBiesack | 3 | 0 | 2 | 1 |
| jacob-buckaroo | 3 | 0 | 1 | 1 |
| mikekistler | 3 | 0 | 0 | 3 |
| slinkydeveloper | 2 | 0 | 1 | 1 |
| reschke | 1 | 0 | 0 | 0 |
| musiKk | 1 | 0 | 0 | 1 |
| sdatapix | 1 | 0 | 0 | 0 |
| handrews | 1 | 0 | 0 | 1 |
| ohbarye | 1 | 0 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
- Pull request#47sdatspun22025-02-24 20:17
- Pull request#24sdatspun22025-02-24 20:17
- Issue comment#41richsalz2024-11-11 14:28Clarify whether the idempotency service should record requests for which the backing service returns error
- Issue comment#48jmileham2024-11-11 14:15Clarify "resource server SHOULD respond with the result of the previously completed operation"
- Issue comment#41jmileham2024-11-11 14:01Clarify whether the idempotency service should record requests for which the backing service returns error
- Issue comment#48Acconut2024-11-07 14:10Clarify "resource server SHOULD respond with the result of the previously completed operation"
- Issue comment#46richsalz2024-11-06 13:31Identifying a replayed response
- Issue comment#46sdatspun22024-11-06 13:23Identifying a replayed response
- Issue comment#36Acconut2024-11-06 10:11What value does Idempotency Fingerprint add?
- Issue comment#35sdatspun22024-11-05 23:36Idempotency Key Validity and Expiry
- Issue comment#34sdatspun22024-11-05 18:13What does "Uniqueness of the key MUST be defined by the resource owner" mean?
- Issue#48darrelmiller2024-11-05 12:59Clarify "resource server SHOULD respond with the result of the previously completed operation"
- Issue comment#41darrelmiller2024-11-05 12:42Clarify whether the idempotency service should record requests for which the backing service returns error
- Issue comment#36darrelmiller2024-11-05 12:14What value does Idempotency Fingerprint add?
- Issue comment#36sdatspun22024-11-05 05:47What value does Idempotency Fingerprint add?
- Issue comment#41jmileham2024-11-03 16:03Clarify whether the idempotency service should record requests for which the backing service returns error
- Issue comment#46darrelmiller2024-11-03 15:41Identifying a replayed response
- Issue comment#41richsalz2024-11-03 15:35Clarify whether the idempotency service should record requests for which the backing service returns error
- Issue comment#40richsalz2024-11-03 15:32Would additional security risk and mitigation discussion be valuable?
- Issue#40richsalz2024-11-03 15:32Would additional security risk and mitigation discussion be valuable?
- Issue comment#43richsalz2024-11-03 15:27Make explicit the goal of being able to offer idempotency as a standalone intermediary service?
- Issue#43richsalz2024-11-03 15:27Make explicit the goal of being able to offer idempotency as a standalone intermediary service?
- Issue comment#44richsalz2024-11-03 15:26Reconsider handling of DELETE (and possibly PUT)?
- Issue#44richsalz2024-11-03 15:26Reconsider handling of DELETE (and possibly PUT)?
- Pull request#47jacob-buckaroo2024-08-21 14:51
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 8 stars here means stars gained during the window, not the repo's star count.