C NETCONF library
active 2023-09-02 → 2025-03-18 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 564 days from 2023-09-02 to 2025-03-18. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 4 total, peak 1 in a day. Comments: 12 total, peak 4 in a day. Stars: 10 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| michalvasko | 8 | 0 | 0 | 7 |
| rc1997258 | 6 | 0 | 0 | 5 |
| nskordel | 1 | 0 | 0 | 0 |
| PravalliSure | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#291michalvasko2024-09-02 09:05Query on right API to use to get sessions information
- Issue#291PravalliSure2024-08-30 15:56Query on right API to use to get sessions information
- Issue#290michalvasko2024-07-26 09:16Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290rc19972582024-07-26 08:42Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290michalvasko2024-07-26 08:14Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290rc19972582024-07-26 07:59Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290michalvasko2024-07-23 10:09Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290rc19972582024-07-23 10:04Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290michalvasko2024-07-23 08:54Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290rc19972582024-07-23 08:50Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290michalvasko2024-07-22 11:34Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290rc19972582024-07-22 10:20Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#290michalvasko2024-07-16 07:26Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue#290rc19972582024-07-11 13:33Information - Which API is responsible for sending Server Hello to netconf client during TLS handshake?
- Issue comment#289michalvasko2023-09-04 08:14Support related to multiple user names for different netconf servers handled by single netconf-client
- Issue#289nskordel2023-09-02 18:07Support related to multiple user names for different netconf servers handled by single netconf-client
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 10 stars here means stars gained during the window, not the repo's star count.