Skip to content

Web API for accessing Human Interface Devices (HID)

active 2023-08-212026-05-03 (UTC)

Complete coverage26,747 / 26,747 hourly files (100%) · 2 absent upstream2023-08-152026-09-02 (UTC)
Events
120
Pushes
2
Pull requests
2
Issues
16
Stars
25
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 987 days from 2023-08-21 to 2026-05-03. Pushes: 2 total, peak 2 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 16 total, peak 2 in a day. Comments: 73 total, peak 6 in a day. Stars: 25 total, peak 2 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

Recent activity

Latest issues, pull requests and releases

  • Issue comment#131didix162026-01-23 14:44
    Missing output reports
  • Issue comment#131nondebug2026-01-23 03:17
    Missing output reports
  • Issue#131didix162026-01-19 10:22
    Missing output reports
  • Issue#130215ly2025-11-17 01:36
    I am unable to receive any response from the hid device
  • Issue#130215ly2025-11-17 01:31
    I am unable to receive any response from the hid device
  • Issue comment#130nondebug2025-11-14 23:18
    I am unable to receive any response from the hid device
  • Issue comment#34whatcall2025-09-14 16:27
    Serial number
  • Issue#128oneman2025-07-27 22:01
    mkay
  • Issue comment#127nondebug2025-06-12 00:05
    Window always pad 0 in InputReportEvent's data
  • Issue comment#127kelvinkoko2025-06-11 22:57
    Window always pad 0 in InputReportEvent's data
  • Issue comment#127nondebug2025-06-11 18:39
    Window always pad 0 in InputReportEvent's data
  • Issue comment#127chengweih0012025-06-11 05:09
    Window always pad 0 in InputReportEvent's data
  • Issue comment#127kelvinkoko2025-06-08 03:21
    Window always pad 0 in InputReportEvent's data
  • Issue#127kelvinkoko2025-06-08 00:30
    Window always pad 0 in InputReportEvent's data
  • Issue comment#125regretronics2025-04-11 00:43
    Device access blocking: consider making way for touchpads/digitizers
  • Issue comment#117shinji-sirona2025-03-26 06:39
    On mac computer, the oninputreport event has been registered, but the data cannot be received when it is sent for the first time. Only the second time it is sent can the data be received. Continuous one success and one failure
  • Issue comment#125nondebug2025-03-26 02:25
    Device access blocking: consider making way for touchpads/digitizers
  • Issue comment#117nondebug2025-03-26 02:10
    On mac computer, the oninputreport event has been registered, but the data cannot be received when it is sent for the first time. Only the second time it is sent can the data be received. Continuous one success and one failure
  • Issue comment#117shinji-sirona2025-03-26 00:25
    On mac computer, the oninputreport event has been registered, but the data cannot be received when it is sent for the first time. Only the second time it is sent can the data be received. Continuous one success and one failure
  • Issue comment#117nondebug2025-03-26 00:09
    On mac computer, the oninputreport event has been registered, but the data cannot be received when it is sent for the first time. Only the second time it is sent can the data be received. Continuous one success and one failure
  • Issue comment#117shinji-sirona2025-03-25 21:41
    On mac computer, the oninputreport event has been registered, but the data cannot be received when it is sent for the first time. Only the second time it is sent can the data be received. Continuous one success and one failure
  • Issue comment#125regretronics2025-03-25 16:53
    Device access blocking: consider making way for touchpads/digitizers
  • Issue comment#125regretronics2025-03-25 03:03
    Device access blocking: consider making way for touchpads/digitizers
  • Issue comment#125regretronics2025-03-25 02:50
    Device access blocking: consider making way for touchpads/digitizers
  • Issue comment#125nondebug2025-03-25 01:21
    Device access blocking: consider making way for touchpads/digitizers

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