Skip to content

An open-source, code-first Python toolkit for building, evaluating, and deploying sophisticated AI agents with flexibility and control.

active 2025-09-192026-02-25 (UTC)

Partial coverage12,579 / 14,301 hourly files (88%) · 2 absent upstream · 1,716 failed, retryable2024-12-232026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
279
Pushes
33
Pull requests
0
Issues
131
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 160 days from 2025-09-19 to 2026-02-25. Pushes: 33 total, peak 6 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 131 total, peak 18 in a day. Comments: 109 total, peak 24 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
ryanaiagent26133099
neodev-ai10009
sachinprasadhs2001

Recent activity

Latest issues, pull requests and releases

  • Issue#15ryanaiagent2026-02-25 09:25
    Test scenario 4: Taking no action if the last comment is from the contributor
  • Issue comment#14neodev-ai2026-02-25 09:24
    Test scenario 3: Identify missing 'request clarification' label and adding it whenever a stale label is being applied.
  • Issue comment#13neodev-ai2026-02-25 09:23
    Test scenario 2: Taking no action when the last comment from maintainer doesn't qualify as requesting information/ clarification/ suggestion or a question
  • Issue comment#12neodev-ai2026-02-25 09:22
    Test scenario 1: Marking stale when maintainer comment is last and no other activity from the contributor or other users
  • Issue comment#13ryanaiagent2026-02-25 06:44
    Test scenario 2: Taking no action when the last comment from maintainer doesn't qualify as requesting information/ clarification/ suggestion or a question
  • Issue comment#16ryanaiagent2026-02-25 06:44
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#17ryanaiagent2026-02-25 06:44
    Test scenario 6: Removing 'stale' label when the contributor has edited the description field of the issue and alert the maintainer
  • Issue#12ryanaiagent2026-02-25 06:24
    Test scenario 1: Marking stale when maintainer comment is last and no other activity from the contributor or other users
  • Issue comment#12ryanaiagent2026-02-25 06:24
    Test scenario 1: Marking stale when maintainer comment is last and no other activity from the contributor or other users
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:23
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue comment#16ryanaiagent2026-02-25 06:22
    Test scenario 5: Removing 'stale' label from issue which has contributor comment after maintainer's comment
  • Issue#15ryanaiagent2026-02-25 06:22
    Test scenario 4: Taking no action if the last comment is from the contributor
  • Issue#14ryanaiagent2026-02-25 06:22
    Test scenario 3: Identify missing 'request clarification' label and adding it whenever a stale label is being applied.
  • Issue comment#15ryanaiagent2026-02-25 06:22
    Test scenario 4: Taking no action if the last comment is from the contributor
  • Issue#18ryanaiagent2026-02-25 06:22
    Test scenario 7: Removing 'stale' label when the contributor has edited the issue title and adding a notification message for the maintainer. Testing Edit 1: posted, Edit 2:posted Edit 3: posted Edit4:posted and adding a maintainer alert message Edit5: Posted
  • Issue comment#18ryanaiagent2026-02-25 06:22
    Test scenario 7: Removing 'stale' label when the contributor has edited the issue title and adding a notification message for the maintainer. Testing Edit 1: posted, Edit 2:posted Edit 3: posted Edit4:posted and adding a maintainer alert message Edit5: Posted
  • Issue#17ryanaiagent2026-02-25 06:22
    Test scenario 6: Removing 'stale' label when the contributor has edited the description field of the issue and alert the maintainer

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.