Gain insights into MS-RPC implementations that may be vulnerable using an automated approach and make it easy to visualize the data. By following this approach, a security researcher will hopefully identify interesting RPC services in such a time that would take a manual approach significantly more.
active 2025-07-14 → 2026-05-05 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 296 days from 2025-07-14 to 2026-05-05. Pushes: 4 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 in a day. Stars: 179 total, peak 49 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| 1ncendium | 4 | 4 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Release1ncendium2025-10-15 17:06v1.1
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 179 stars here means stars gained during the window, not the repo's star count.