Leaderboard github.com
ValveSoftware/ToGL
Direct3D to OpenGL abstraction layer
AI provenance
0%
none-detected
- Confidence
- 41%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
37/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
81/100
adequate
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% none-detected
No AI attribution or AI-consistent velocity signals detected.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.08
Lines added per month all AI-attributed share
- 2014-0338,713 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 2
- effective_loc
- 38,713
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 37,965
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 187
- measured_loc
- 748
- median_loc_per_hour
- 187
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 748
- work_units
- 1
Release velocityskipped
Coding styleok3 items
- step-by-step narration comment: // now we know enough to allocate and populate the new tex layout.
- step-by-step narration comment: // finally, disable all of them if commandline did not say "enable spew"
- step-by-step narration comment: // then, move cursor to next line.
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 3
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 2
- files:placeholder
- 0
- index
- 0.08
- lines_scanned
- 38,713
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.08
- per_kloc:placeholder
- 0
Code quality
37 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 45% of function code in complex or long functions; 13% duplicated lines. Weakest area: testing.
How the score is built
- Complexity26
- Duplication45
- Lint and smells100
- Tests and CI0
- Documentation45
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- D3DToGL_ASM::TranslateShader in togl/linuxwin/dx9asmtogl.cpp: complexity 160, 697 lines
- D3DToGL::TranslateShader in togl/linuxwin/dx9asmtogl2.cpp: complexity 160, 549 lines
- GLMContext::DebugHook in togl/linuxwin/glmgr.cpp: complexity 126, 392 lines
- GLMContext::DebugDump in togl/linuxwin/glmgr.cpp: complexity 112, 503 lines
- D3DToGL::PrintParameterToString in togl/linuxwin/dx9asmtogl2.cpp: complexity 108, 471 lines
- D3DToGL_ASM::PrintParameterToString in togl/linuxwin/dx9asmtogl.cpp: complexity 87, 364 lines
- D3DToGL_ASM::PrintOpcode in togl/linuxwin/dx9asmtogl.cpp: complexity 83, 195 lines
- D3DToGL::PrintOpcode in togl/linuxwin/dx9asmtogl2.cpp: complexity 83, 195 lines
- IDirect3DDevice9::SetRenderState in togl/linuxwin/dxabstract.cpp: complexity 83, 314 lines
- D3DToGL::OpenIntrinsic in togl/linuxwin/dx9asmtogl2.cpp: complexity 80, 204 lines
- complex_functions
- 49
- function_nloc
- 19,519
- functions
- 928
- long_functions
- 32
- many_param_functions
- 25
- mean_ccn
- 4.85
- p90_ccn
- 9
- risky_nloc_share
- 45.0%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: public/togl/linuxwin/cglmbuffer.h:1 and public/togl/linuxwin/cglmfbo.h:1
- 6+ duplicated lines: public/togl/linuxwin/cglmbuffer.h:19 and public/togl/linuxwin/cglmprogram.h:19
- 6+ duplicated lines: public/togl/linuxwin/cglmtex.h:296 and public/togl/linuxwin/cglmtex.h:336
- 6+ duplicated lines: public/togl/linuxwin/dxabstract.h:117 and togl/linuxwin/dxabstract.cpp:6251
- 6+ duplicated lines: public/togl/linuxwin/dxabstract_types.h:1133 and public/togl/linuxwin/glmgr.h:1062
- 6+ duplicated lines: public/togl/linuxwin/dxabstract_types.h:1644 and togl/linuxwin/glmgr.cpp:4777
- 6+ duplicated lines: public/togl/linuxwin/glmgr.h:1857 and togl/linuxwin/glmgr.cpp:4796
- 6+ duplicated lines: togl/linuxwin/cglmbuffer.cpp:118 and togl/linuxwin/cglmbuffer.cpp:141
- 6+ duplicated lines: togl/linuxwin/cglmprogram.cpp:260 and togl/linuxwin/cglmprogram.cpp:284
- 6+ duplicated lines: togl/linuxwin/cglmtex.cpp:931 and togl/linuxwin/cglmtex.cpp:1916
- compared_lines
- 25,590
- duplicated_lines
- 3,392
- duplicated_share
- 13.3%
- files
- 35
Lintok
- findings
- 0
- scanned_lines
- 38,713
- weighted_findings
- 0
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- no
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 0
- cochange_commits
- 2
- cochange_share
- 0.0%
- source_lines
- 38,713
- test_lines
- 0
- test_ratio
- 0
Documentationok2 items
- README.md
README.md - LICENSE
LICENSE
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- no
- readme_lines
- 13
Type safetyskipped
Security
81 adequate
Security posture is adequate: no high-impact findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)98
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 9
- findings_high
- 0
- findings_low
- 0
- findings_medium
- 9
- parse_errors
- 12
- scanned_lines
- 38,713
- weighted_findings
- 2.25
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok
- check:dependency_updates
- no
- check:lockfiles
- yes
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 0
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
9 medium
9 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| medium | opengrep/c.lang.security.insecure-use-memset |
public/togl/linuxwin/glmgr.h:1181 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
public/togl/linuxwin/glmgr.h:1408 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
public/togl/linuxwin/glmgr.h:1578 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
public/togl/linuxwin/glmgr.h:1882 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
public/togl/linuxwin/glmgr.h:75 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
public/togl/linuxwin/glmgr.h:899 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
public/togl/linuxwin/glmgr.h:956 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
public/togl/linuxwin/glmgrbasics.h:183 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
togl/linuxwin/mach_override.c:675 | 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... | Static analysis (opengrep) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 0 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | skipped | — | 0 | no registry dependencies declared |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 9 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 7b64367f0e67 | prov-5+qual-2+sec-2 | 0% | 37 | 81 |
| 2026-11-14 | 7b64367f0e67 | prov-4+qual-2+sec-2 | 0% | 37 | 81 |
Full text report
- Repository: https://github.com/ValveSoftware/ToGL
- Commit:
7b64367f0e67b29bdc3343f43e440059c591216b - Generated: 2026-11-14T14:52:02+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 41% | 100% |
| Code quality | 37 | poor | 90% | 100% |
| Security | 81 | 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.08 per 1,000 lines (narrated steps 3, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2014-03 | 38,713 | 0% |
Evidence
- step-by-step narration comment: // now we know enough to allocate and populate the new tex layout. (togl/linuxwi)
- step-by-step narration comment: // finally, disable all of them if commandline did not say "enable spew" (togl/linuxwi)
- step-by-step narration comment: // then, move cursor to next line. (togl/linuxwi)
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; 45% of function code in complex or long functions; 13% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 26 |
| Duplication | 45 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 0 |
| Documentation | 45 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 928; mean complexity 4.8, 90th percentile 9; 49 complex and 32 long functions
- Duplicated lines: 13.3% of 25,590 compared
- Tests: 0 test lines for 38,713 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: readme, contributing, changelog
Most complex functions:
- D3DToGL_ASM::TranslateShader in togl/linuxwin/dx9asmtogl.cpp: complexity 160, 697 lines
- D3DToGL::TranslateShader in togl/linuxwin/dx9asmtogl2.cpp: complexity 160, 549 lines
- GLMContext::DebugHook in togl/linuxwin/glmgr.cpp: complexity 126, 392 lines
- GLMContext::DebugDump in togl/linuxwin/glmgr.cpp: complexity 112, 503 lines
- D3DToGL::PrintParameterToString in togl/linuxwin/dx9asmtogl2.cpp: complexity 108, 471 lines
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 98 |
| 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] |
public/togl/linuxwin/glmgr.h:75 |
| 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] |
public/togl/linuxwin/glmgr.h:899 |
| 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] |
public/togl/linuxwin/glmgr.h:956 |
| 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] |
public/togl/linuxwin/glmgr.h:1181 |
| 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] |
public/togl/linuxwin/glmgr.h:1408 |
| 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] |
public/togl/linuxwin/glmgr.h:1578 |
| 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] |
public/togl/linuxwin/glmgr.h:1882 |
| 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] |
public/togl/linuxwin/glmgrbasics.h:183 |
| 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] |
togl/linuxwin/mach_override.c:675 |
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: 38,713; test lines: 0
| Language | Lines |
|---|---|
| C++ | 28,632 |
| C | 10,081 |