Intel® Cryptography Primitives Library is a secure, fast and lightweight library of building blocks for cryptography, highly-optimized for various Intel® CPUs
active 2024-10-11 → 2026-06-29 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 627 days from 2024-10-11 to 2026-06-29. Pushes: 113 total, peak 4 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 12 total, peak 3 in a day. Comments: 24 total, peak 4 in a day. Stars: 32 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 |
|---|---|---|---|---|
| perflibs | 111 | 111 | 0 | 0 |
| rcao8 | 15 | 0 | 0 | 11 |
| wxy279 | 10 | 0 | 0 | 6 |
| murali-i | 2 | 0 | 2 | 0 |
| naushadck | 2 | 0 | 0 | 1 |
| stanciuadrian | 2 | 0 | 0 | 2 |
| haxelion | 1 | 0 | 0 | 1 |
| Jingkai | 1 | 0 | 0 | 0 |
| iMartyan | 1 | 0 | 0 | 1 |
| DAIDJACREX | 1 | 0 | 0 | 1 |
| andreyfe1 | 1 | 0 | 0 | 0 |
| greenozon | 1 | 0 | 0 | 0 |
| mikolajlubiak | 1 | 0 | 0 | 1 |
| paveldyakov | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#98paveldyakov2026-04-15 10:35Support for AVX10.x family
- Issue comment#95mikolajlubiak2026-01-02 18:18fix: avoid resetting `method.hashUpdate`
- Pull request#100murali-i2025-11-07 00:06
- Issue comment#96iMartyan2025-10-01 10:23TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Pull request#99murali-i2025-09-03 14:10
- Issue#98greenozon2025-07-11 13:18Support for AVX10.x family
- Issue comment#96stanciuadrian2025-07-04 08:52TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Issue comment#96wxy2792025-07-03 02:36TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Issue comment#96wxy2792025-05-31 00:10TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Issue comment#96wxy2792025-05-31 00:07TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Releasekiselik2025-05-30 14:39Intel Cryptography Primitives Library 1.2.0
- Issue#96wxy2792025-05-17 07:36TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Issue#96wxy2792025-05-17 07:35TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Issue#97wxy2792025-04-27 13:35ippsGFpECKeyExchangeSM2_SharedKey is thread-safe ?
- Issue comment#96wxy2792025-04-27 12:42TLS client handshake with ECDHE-SM2-X causes coredump under multi-core pressure testing
- Issue comment#96wxy2792025-04-26 07:33SM2 TLS client causes coredump under multi-core pressure testing
- Issue comment#96wxy2792025-04-26 07:31SM2 TLS client causes coredump under multi-core pressure testing
- Issue#96wxy2792025-04-26 02:48SM2 TLS client causes coredump under multi-core pressure testing
- Issue comment#94stanciuadrian2025-03-23 19:32Error when building with GCC/MinGW-w64
- Issue comment#95haxelion2025-03-11 06:14fix: avoid resetting `method.hashUpdate`
- Issue comment#94rcao82025-02-27 02:51Error when building with GCC/MinGW-w64
- Issue comment#50rcao82025-02-25 03:42Is IppsECCPState thread safe?
- Issue comment#76rcao82025-02-19 01:40Some questions about SM2 key exchange
- Issue#76rcao82025-02-19 01:40Some questions about SM2 key exchange
- Issue comment#79rcao82025-02-19 01:31Help Implementing FIPS Level 1 Requirements #4
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 32 stars here means stars gained during the window, not the repo's star count.