Skip to content

active 2025-04-032025-04-30 (UTC)

Complete coverage26,485 / 26,485 hourly files (100%) · 2 absent upstream2023-08-152026-08-22 (UTC)
Events
54
Pushes
10
Pull requests
10
Issues
19
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 28 days from 2025-04-03 to 2025-04-30. Pushes: 10 total, peak 2 in a day. Pull requests: 10 total, peak 2 in a day. Issues: 19 total, peak 6 in a day. Comments: 5 total, peak 3 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
BKM144410105

Recent activity

Latest issues, pull requests and releases

  • Issue comment#16BKM142025-04-29 15:42
    Create a README.md file for setup instructions
  • Issue#16BKM142025-04-29 15:42
    Create a README.md file for setup instructions
  • Issue#16BKM142025-04-29 12:24
    Create a README.md file for setup instructions
  • Issue#13BKM142025-04-19 16:31
    Dockerize the application
  • Issue#12BKM142025-04-19 05:28
    use context.WithTimeout for timeouts
  • Pull request#15BKM142025-04-19 05:28
  • Pull request#15BKM142025-04-19 05:28
  • Issue#14BKM142025-04-17 16:17
    R&D - Submission ID based workspace
  • Issue#13BKM142025-04-17 16:09
    Dockerize the application
  • Issue comment#2BKM142025-04-17 16:04
    Implement functionality to keep track of tasks assigned to a container
  • Issue comment#3BKM142025-04-17 16:04
    Based on the language the user has submitted the code in, use that specific language container to execute.
  • Issue#3BKM142025-04-17 16:04
    Based on the language the user has submitted the code in, use that specific language container to execute.
  • Issue comment#5BKM142025-04-17 16:02
    Create a map with keys being languages and arrays being the values containing container ids
  • Issue#5BKM142025-04-17 16:02
    Create a map with keys being languages and arrays being the values containing container ids
  • Issue#10BKM142025-04-17 15:59
    Change container approach - Run containers based on user's submission language
  • Pull request#11BKM142025-04-17 15:59
  • Pull request#11BKM142025-04-17 15:58
  • Issue#10BKM142025-04-17 13:38
    Change container approach - Run containers based on user's submission language
  • Issue#8BKM142025-04-16 18:05
    Create a timeout to end execution in case of infinite loops/recursive calls
  • Pull request#9BKM142025-04-16 18:05
  • Pull request#9BKM142025-04-16 18:04
  • Issue#8BKM142025-04-13 03:21
    Create a timeout to end execution in case of infinite loops/recursive calls
  • Pull request#7BKM142025-04-12 06:59
  • Issue#6BKM142025-04-12 06:59
    Save the user submitted code to a file before executing and delete the file once it is complete
  • Pull request#7BKM142025-04-12 06:59

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.