Skip to content

active 2024-11-262025-03-02 (UTC)

Complete coverage26,588 / 26,588 hourly files (100%) · 2 absent upstream2023-08-152026-08-26 (UTC)
Events
29
Pushes
11
Pull requests
0
Issues
13
Stars
4
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 97 days from 2024-11-26 to 2025-03-02. Pushes: 11 total, peak 3 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 13 total, peak 3 in a day. Comments: 0 total, peak 0 in a day. Stars: 4 total, peak 1 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
MakerDZ241100

Recent activity

Latest issues, pull requests and releases

  • Issue#9MakerDZ2024-12-09 12:49
    API filtering option with queries for related data from the database relationship.
  • Issue#8MakerDZ2024-12-06 16:47
    Docker setup for deploying an API service.
  • Issue#8MakerDZ2024-12-03 14:16
    Docker setup for deploying an API service.
  • Issue#7MakerDZ2024-12-02 22:50
    To fix the query performance issue.
  • Issue#3MakerDZ2024-12-02 22:40
    Set up Fastify services and establish the structure of the API.
  • Issue#6MakerDZ2024-11-29 11:43
    Create API documentation and other necessary documents for the API.
  • Issue#5MakerDZ2024-11-29 11:42
    Designing and refining the data entry UI (dashboard).
  • Issue#4MakerDZ2024-11-29 11:41
    Designing the API services for necessary communication between the client and the server.
  • Issue#1MakerDZ2024-11-28 11:32
    Implement a shared Prisma client within the monorepo for both backend services and the frontend.
  • Issue#2MakerDZ2024-11-28 11:32
    Ensure the frontend can run as intended by using a shared Prisma client instead of its own separate Prisma client.
  • Issue#3MakerDZ2024-11-26 18:59
    Set up Fastify services and establish the structure of the API.
  • Issue#2MakerDZ2024-11-26 18:57
    Ensure the frontend can run as intended by using a shared Prisma client instead of its own separate Prisma client.
  • Issue#1MakerDZ2024-11-26 18:55
    To implement shared prisma within mono repo for backend services and frontend

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