Leaderboard github.com
steveLauwh/SGI-STL
剖析 STL 是一种享受的过程！
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
45/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
85/100
strong
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
- Repository: https://github.com/steveLauwh/SGI-STL
- Commit:
be34aace923769ee114366e0e7decf8521d422b9 - Generated: 2026-11-13T23:41:26+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 | 45 | poor | 90% | 100% |
| Security | 85 | strong | 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%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2017-07 | 31,425 | 0% |
| 2017-08 | 16,300 | 0% |
| 2017-12 | 715 | 0% |
| 2018-01 | 2,324 | 0% |
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 poor: test-to-source ratio 0.00, no CI test run detected; 2% of function code in complex or long functions; 78% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 94 |
| Duplication | 1 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 0 |
| Documentation | 40 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 4,359; mean complexity 1.6, 90th percentile 3; 7 complex and 2 long functions
- Duplicated lines: 78.4% of 36,056 compared
- Tests: 0 test lines for 49,673 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: license, contributing, changelog
Most complex functions:
- [_Rb_tree_rebalance_for_erase in SGI-STL V3.3/stl_tree.h: complexity 40, 127 lines](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/SGI-STL V3.3/stl_tree.h#L300)
- [_Rb_tree_rebalance_for_erase in The Annotated STL Sources V3.3/container/associative container/RB-tree/stl_tree.h: complexity 40, 127 lines](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/The Annotated STL Sources V3.3/container/associative container/RB-tree/stl_tree.h#L311)
- [_Rb_tree<_Key,_Value,_KeyOfValue,_Compare,_Alloc>::__rb_verify in SGI-STL V3.3/stl_tree.h: complexity 21, 27 lines](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/SGI-STL V3.3/stl_tree.h#L1305)
- [_Rb_tree<_Key,_Value,_KeyOfValue,_Compare,_Alloc>::__rb_verify in The Annotated STL Sources V3.3/container/associative container/RB-tree/stl_tree.h: complexity 21, 27 lines](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/The Annotated STL Sources V3.3/container/associative container/RB-tree/stl_tree.h#L1328)
- [rope<_CharT,_Alloc>::_S_substring in SGI-STL V3.3/ropeimpl.h: complexity 17, 98 lines](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/SGI-STL V3.3/ropeimpl.h#L645)
Security
Security posture is strong: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 100 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 20 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: signed commits, lockfiles; missing: security policy, dependency updates
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] |
[SGI-STL V3.3/stl_algobase.h:461](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/SGI-STL V3.3/stl_algobase.h#L461) |
| 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] |
[SGI-STL V3.3/stl_algobase.h:467](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/SGI-STL V3.3/stl_algobase.h#L467) |
| 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] |
[SGI-STL V3.3/stl_algobase.h:472](https://github.com/steveLauwh/SGI-STL/blob/be34aace923769ee114366e0e7decf8521d422b9/SGI-STL V3.3/stl_algobase.h#L472) |
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: 49,673; test lines: 0
| Language | Lines |
|---|---|
| C | 48,555 |
| C++ | 1,118 |