Skip to content

ringecosystem/xapi-contracts

View on GitHub ↗Related repositories →

active 2024-09-042025-08-11 (UTC)

Complete coverage26,370 / 26,370 hourly files (100%) · 2 absent upstream2023-08-152026-08-17 (UTC)
Events
211
Pushes
104
Pull requests
25
Issues
42
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 342 days from 2024-09-04 to 2025-08-11. Pushes: 104 total, peak 7 in a day. Pull requests: 25 total, peak 4 in a day. Issues: 42 total, peak 4 in a day. Comments: 10 total, peak 2 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

ContributorContributionsPushesPRsComments
jiguantong1801042510
hujw773000
fewensa1000

Recent activity

Latest issues, pull requests and releases

  • Issue#25fewensa2025-08-11 09:38
    XAPI for Sepolia ORMP
  • Issue#38jiguantong2025-02-11 09:13
    Roadmap
  • Pull request#37jiguantong2025-02-11 02:38
  • Pull request#37jiguantong2025-02-07 02:22
  • Issue#35jiguantong2024-12-31 06:57
    Audit #4
  • Issue comment#34jiguantong2024-12-31 06:57
    No one pays for the synchronization configuration, so the publisher paymaster has no motivation to do this?
  • Issue#34jiguantong2024-12-31 06:57
    No one pays for the synchronization configuration, so the publisher paymaster has no motivation to do this?
  • Issue comment#33jiguantong2024-12-31 06:57
    Who pays for publishing and syncing configurations on Near?
  • Issue#33jiguantong2024-12-31 06:57
    Who pays for publishing and syncing configurations on Near?
  • Pull request#36jiguantong2024-12-20 02:29
  • Pull request#36jiguantong2024-12-19 09:14
  • Issue#35jiguantong2024-12-11 03:04
    Audit #4
  • Issue#31jiguantong2024-12-11 02:45
    Audit #3
  • Pull request#32jiguantong2024-12-11 02:45
  • Issue comment#34jiguantong2024-12-10 09:41
    No one pays for the synchronization configuration, so the publisher paymaster has no motivation to do this?
  • Issue comment#33jiguantong2024-12-10 09:41
    Who pays for publishing and syncing configurations on Near?
  • Issue#33jiguantong2024-12-03 03:31
    Who pays for publishing and syncing configurations on Near?
  • Issue#31jiguantong2024-11-22 05:50
    Audit #3
  • Issue#29jiguantong2024-11-19 04:48
    Refactor XAPI
  • Pull request#30jiguantong2024-11-19 04:46
  • Pull request#30jiguantong2024-11-18 08:04
  • Releasejiguantong2024-11-18 06:59
    v0.0.1
  • Issue#29jiguantong2024-11-18 06:03
    Refactor XAPI
  • Issue#28jiguantong2024-11-13 07:15
    Request spec
  • Pull request#27jiguantong2024-11-13 05:38

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.