Skip to content

This is a .NET class library that implements a WHOIS client.

active 2023-10-092026-04-02 (UTC)

Complete coverage26,413 / 26,413 hourly files (100%) · 2 absent upstream2023-08-152026-08-19 (UTC)
Events
72
Pushes
16
Pull requests
8
Issues
5
Stars
8
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 907 days from 2023-10-09 to 2026-04-02. Pushes: 16 total, peak 4 in a day. Pull requests: 8 total, peak 2 in a day. Issues: 5 total, peak 2 in a day. Comments: 24 total, peak 5 in a day. Stars: 8 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
jsakamoto3216312
Makaopior200511
Copilot3001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#15Makaopior2025-04-11 00:47
    Throw TimeoutException instead of OperationCanceledException when RawQueryAsync method times out
  • Issue comment#15jsakamoto2025-04-10 12:22
    Throw TimeoutException instead of OperationCanceledException when RawQueryAsync method times out
  • Pull request#15jsakamoto2025-04-10 11:53
  • Pull request#15Makaopior2025-03-24 01:00
  • Issue#10Makaopior2025-03-13 00:24
    Proposal: Reconsider default timeout & retries settings
  • Issue comment#11Makaopior2025-03-13 00:24
    Bug: Potential infinite loop while reading response from socket
  • Issue#11Makaopior2025-03-13 00:24
    Bug: Potential infinite loop while reading response from socket
  • Issue comment#10Makaopior2025-03-13 00:23
    Proposal: Reconsider default timeout & retries settings
  • Issue comment#10jsakamoto2025-03-12 14:00
    Proposal: Reconsider default timeout & retries settings
  • Issue comment#11jsakamoto2025-03-12 13:58
    Bug: Potential infinite loop while reading response from socket
  • Pull request#14jsakamoto2025-03-12 13:14
  • Pull request#14Makaopior2025-03-11 01:16
  • Issue#12jsakamoto2025-03-10 13:15
    Potential bug: Decoding partial response may result in corrupt string in case of multi-byte encoding
  • Issue comment#12Makaopior2025-03-10 07:04
    Potential bug: Decoding partial response may result in corrupt string in case of multi-byte encoding
  • Pull request#13Makaopior2025-03-10 07:04
  • Issue comment#12jsakamoto2025-03-10 04:00
    Potential bug: Decoding partial response may result in corrupt string in case of multi-byte encoding
  • Pull request#9jsakamoto2025-03-10 03:54
  • Issue comment#9Makaopior2025-03-09 23:57
    Moved TcpClient creation to separate class (in case there's something special to do before WHOIS request)
  • Issue comment#9jsakamoto2025-03-08 02:17
    Moved TcpClient creation to separate class (in case there's something special to do before WHOIS request)
  • Issue comment#9jsakamoto2025-03-07 12:44
    Moved TcpClient creation to separate class (in case there's something special to do before WHOIS request)
  • Issue comment#9Makaopior2025-03-07 00:03
    Moved TcpClient creation to separate class (in case there's something special to do before WHOIS request)
  • Issue comment#9jsakamoto2025-03-06 13:55
    Moved TcpClient creation to separate class (in case there's something special to do before WHOIS request)
  • Issue comment#10jsakamoto2025-03-06 13:01
    Proposal: Reconsider default timeout & retries settings
  • Issue comment#11jsakamoto2025-03-06 13:00
    Bug: Potential infinite loop while reading response from socket
  • Issue#11Makaopior2025-03-06 04:24
    Bug: Potential infinite loop while reading response from socket

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