Skip to content

active 2025-04-102025-04-15 (UTC)

Complete coverage26,624 / 26,624 hourly files (100%) · 2 absent upstream2023-08-152026-08-28 (UTC)
Events
43
Pushes
15
Pull requests
0
Issues
21
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 6 days from 2025-04-10 to 2025-04-15. Pushes: 15 total, peak 15 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 21 total, peak 21 in a day. Comments: 5 total, peak 5 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
findingfaey361500
soc-se-bot2002
nus-pe-bot1001
nus-se-script1001
soc-pe-bot1001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#10soc-pe-bot2025-04-15 20:02
    Subject field case sensitivity inconsistent across different commands
  • Issue comment#6nus-pe-bot2025-04-15 19:35
    View command behaviour doesn't match the specification on UG
  • Issue comment#4soc-se-bot2025-04-15 19:06
    Edit command allows duplicated contact details without validation
  • Issue comment#2nus-se-script2025-04-15 18:38
    Duplicate phone numbers allowed despite supposedly unique identity requirements
  • Issue comment#1soc-se-bot2025-04-15 18:10
    Email validation accepts invalid format
  • Issue#3findingfaey2025-04-11 13:10
    Duplicate email addresses allowed
  • Issue#7findingfaey2025-04-11 13:08
    View command order contradicts general parameter order stated in documentation
  • Issue#13findingfaey2025-04-11 13:06
    Name field input validation is not robust enough
  • Issue#5findingfaey2025-04-11 13:05
    Missing input validation allows excessively long names and phone numbers
  • Issue#9findingfaey2025-04-11 13:05
    Missing input validation allows extra characters in commands without error
  • Issue#11findingfaey2025-04-11 13:05
    Unclear error message for non-existent subjects in finish command
  • Issue#8findingfaey2025-04-11 13:04
    UG lacks sufficient screenshots to illustrate command functionalities
  • Issue#14findingfaey2025-04-11 13:04
    UML diagram in DG doesn't follow module convention
  • Issue#14findingfaey2025-04-11 09:38
    UML diagram in DG doesn't follow module convention
  • Issue#13findingfaey2025-04-11 09:24
    Name field input validation is not robust enough
  • Issue#12findingfaey2025-04-11 09:17
    Missing validation allows arbitrary text as value in subject field
  • Issue#11findingfaey2025-04-11 09:13
    Unclear error message for non-existent subjects in finish command
  • Issue#10findingfaey2025-04-11 09:09
    Subject field case sensitivity inconsistent across different commands
  • Issue#9findingfaey2025-04-11 09:03
    Missing input validation allows extra characters in commands without error
  • Issue#8findingfaey2025-04-11 08:58
    UG lacks sufficient screenshots to illustrate command functionalities
  • Issue#6findingfaey2025-04-11 08:52
    View command behaviour doesn't match the specification on UG
  • Issue#5findingfaey2025-04-11 08:44
    Missing input validation allows excessively long names and phone numbers
  • Issue#4findingfaey2025-04-11 08:39
    Edit command allows duplicated contact details without validation
  • Issue#3findingfaey2025-04-11 08:33
    Duplicate email addresses allowed
  • Issue#2findingfaey2025-04-11 08:28
    Duplicate phone numbers allowed despite supposedly unique identity requirements

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.