alibaba/tair
A distributed key-value storage system developed by Alibaba Group
- Repository: https://github.com/alibaba/tair
- Commit:
5cce166b779385f422e8c2fce727cd9b4545491c - Generated: 2026-11-13T23:41:50+00:00
- Scorer 0.1.0, scoring prov-4+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 65% | 100% |
| Code quality | 56 | weak | 90% | 100% |
| Security | 78 | adequate | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
Stylometry index: 0.05 per 1,000 lines (narrated steps 8, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2012-02 | 174 | 0% |
| 2012-03 | 5,864 | 0% |
| 2012-04 | 6,590 | 0% |
| 2012-05 | 12,190 | 0% |
| 2012-06 | 18,526 | 0% |
| 2012-07 | 5,899 | 0% |
| 2012-08 | 12,035 | 0% |
| 2012-09 | 19,799 | 0% |
| 2012-10 | 954 | 0% |
| 2013-11 | 3 | 0% |
| 2016-04 | 131,374 | 0% |
| 2018-02 | 5 | 0% |
Evidence
- step-by-step narration comment: // Step 1: Scan forward in the input looking for a 4-byte-long match. (src/common/s)
- step-by-step narration comment: // Step 2: A 4-byte match has been found. We'll later see if more (src/common/s)
- step-by-step narration comment: // Step 3: Call EmitCopy, and then see if another EmitCopy could (src/common/s)
- step-by-step narration comment: // Now, we just copy raw data whose byteorder is based on architecture itself. (src/common/s)
- step-by-step narration comment: // now we only use one writer. (src/dataserv)
- step-by-step narration comment: // now, we are proposing to be done (src/storage/)
- step-by-step narration comment: // first, get real hungry ones (src/storage/)
- step-by-step narration comment: // now, we will feed hungrys (src/storage/)
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is weak: test-to-source ratio 0.06, no CI test run detected; 20% of function code in complex or long functions; 11% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 55 |
| Duplication | 53 |
| Code smells (Opengrep) | 90 |
| Tests and CI | 26 |
| Documentation | 85 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 7,113; mean complexity 3.2, 90th percentile 7; 183 complex and 53 long functions
- Duplicated lines: 10.7% of 105,162 compared
- Tests: 9,251 test lines for 155,941 source lines (ratio 0.06); CI test commands: none detected; 6% of recent source commits also change tests
- Docs missing or thin: contributing
Most complex functions:
- http_parser_execute in deps/libeasy/src/packet/http/http_parser.c: complexity 354, 1041 lines
- tair::tair_client::print_help in src/client/tair_client.cpp: complexity 147, 562 lines
- tair::packet_factory::create_packet in src/packets/packet_factory.cpp: complexity 84, 264 lines
- tair::base_packet::name in src/packets/base_packet.hpp: complexity 83, 170 lines
- tair::tair_server::packet_handler in src/dataserver/tair_server.cpp: complexity 69, 323 lines
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 97 |
| Static analysis (Opengrep) | 95 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/dns_server.c:35 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/dns_server.c:55 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client.c:41 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client.c:64 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client_simple.c:43 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client_simple.c:69 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client_tbnet.c:51 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client_tbnet.c:74 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client_tbnet.c:96 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client_uthread.c:38 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_client_uthread.c:61 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_packet_tbnet.h:121 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_packet_tbnet.h:142 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_server.c:30 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_server.c:51 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_server_async.c:32 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_server_async.c:53 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_server_tbnet.c:30 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/echo_server_tbnet.c:50 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/http_client.c:49 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
deps/libeasy/sample/http_client.c:244 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/http_server.c:38 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/http_server.c:59 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/http_server_proxy.c:32 |
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
deps/libeasy/sample/http_server_proxy.c:52 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Repository profile
- Source lines: 155,941; test lines: 9,251
| Language | Lines |
|---|---|
| C++ | 113,612 |
| C | 50,972 |
| Shell | 608 |