Every spec was checked page by page against a vendor manual; every “—” is someone confirming it is genuinely not published. Names stay here because when a number is wrong, someone must be findable.
No snapshot yet — run python tools/fetch_contributors.py
Not generated from git log: machines can count commits, but they cannot say who verified which datasheet.
Builds and maintains the whole engineering side: the data gate and validation, per-category page generation, the parts explorer and comparison, the semantics page, suppliers and contributors; verified every A-tier spec for DAMIAO, RobStride, DJI and Unitree (torque normalised to the output side, missing values written as null) and turned traceability into machine-checked rules.
GitHub15 whole-robot entries with URDF/repo links, a bulk expansion of high- and low-level controllers plus IMU/camera/LiDAR — 50 data rows in total — and the part-data collection guide. The remote-controller category came from his ccc branch (5 transmitters + 2 CAN modules with 7 photos), together with the grouped-card layout for part notes and the home-page category preselect. He also added the software section's two groups: algorithms & methods (DreamWaQ, BeamDojo, AMP, PPO) and model architectures (MLP/MoE).
GitHubExpanded the chip category from 14 to 18 parts (STM32H723 / TCAN334G / TMC2209 / AS5600), added official doc pages, datasheet PDFs and official repos for all 18 (each link verified), domestic 1+ prices for 17 of them with source and collection date, and 12 product photos. Also registered the doc_url / doc_pdf / repo_urls keys, clearing 20 false warnings (82 → 62).
GitHubNo contribution leaderboard. This site does not run a points game — ordering is always by spec and measured data, never by who contributed more.