Skip to content

Porting of CursorRIPER for Windsurf

active 2025-04-052026-05-10 (UTC)

Complete coverage26,485 / 26,485 hourly files (100%) · 2 absent upstream2023-08-152026-08-22 (UTC)
Events
348
Pushes
75
Pull requests
0
Issues
1
Stars
206
Forks
33

Activity over time

Daily event counts in the loaded window

Line chart, 401 days from 2025-04-05 to 2026-05-10. Pushes: 75 total, peak 67 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 1 total, peak 1 in a day. Comments: 16 total, peak 7 in a day. Stars: 206 total, peak 8 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
johnpeterman72847509
Silverbullet0695005
uriklar3002

Recent activity

Latest issues, pull requests and releases

  • Issue comment#6Silverbullet0692025-07-05 15:54
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6johnpeterman722025-07-05 15:33
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6Silverbullet0692025-07-04 20:14
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6Silverbullet0692025-07-04 18:21
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6johnpeterman722025-07-04 17:01
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6Silverbullet0692025-07-04 16:40
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6johnpeterman722025-07-04 16:20
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6Silverbullet0692025-07-04 14:17
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6johnpeterman722025-07-04 13:31
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#5johnpeterman722025-06-28 17:43
    Q: Best Practices for activeContext.md and progress.md Usage in Large Teams
  • Issue comment#6johnpeterman722025-06-28 17:42
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#6johnpeterman722025-06-03 16:55
    After starting a new project, the AI automatically switched to execution mode.
  • Issue comment#5uriklar2025-05-20 01:28
    Q: Best Practices for activeContext.md and progress.md Usage in Large Teams
  • Issue comment#5johnpeterman722025-05-15 14:14
    Q: Best Practices for activeContext.md and progress.md Usage in Large Teams
  • Issue comment#5uriklar2025-05-15 00:31
    Q: Best Practices for activeContext.md and progress.md Usage in Large Teams
  • Issue comment#5johnpeterman722025-05-14 15:40
    Q: Best Practices for activeContext.md and progress.md Usage in Large Teams
  • Issue#5uriklar2025-05-14 01:35
    Q: Best Practices for activeContext.md and progress.md Usage in Large Teams

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 206 stars here means stars gained during the window, not the repo's star count.