Skip to content

jonatron/boringssl-python-cffi

View on GitHub ↗Related repositories →

active 2024-08-022025-03-13 (UTC)

Partial coverage16,281 / 20,446 hourly files (80%) · 2 absent upstream · 4,164 failed, retryable2024-04-122026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
6
Pushes
0
Pull requests
0
Issues
2
Stars
2
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 224 days from 2024-08-02 to 2025-03-13. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 2 total, peak 1 in a day. Comments: 2 total, peak 2 in a day. Stars: 2 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
dream23333001
jonatron1001

Recent activity

Latest issues, pull requests and releases

  • Issue#2dream23332024-09-04 03:32
    Why not rewrite SSLContext to implement the BoringSSL handshake, but instead the SSL handshake process is incorporated into NetworkBackend?
  • Issue comment#2dream23332024-08-03 11:08
    Why not rewrite SSLContext to implement the BoringSSL handshake, but instead the SSL handshake process is incorporated into NetworkBackend?
  • Issue comment#2jonatron2024-08-03 08:10
    Why not rewrite SSLContext to implement the BoringSSL handshake, but instead the SSL handshake process is incorporated into NetworkBackend?
  • Issue#2dream23332024-08-02 17:47
    Why not rewrite SSLContext to implement the BoringSSL handshake, but instead the SSL handshake process is incorporated into NetworkBackend?

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