Leaderboard github.com
Tencent/PhoenixGo
Go AI program which implements the AlphaGo Zero paper
AI provenance
0%
none-detected
- Confidence
- 60%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
49/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
78/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 pace0
- Coding-style index (1.0+ means possible)0.00
Lines added per month all AI-attributed share
- 2018-056,777 · 0% AI
- 2018-06102 · 0% AI
- 2018-0849 · 0% AI
- 2018-090 · 0% AI
- 2018-12170 · 0% AI
- 2019-02481 · 0% AI
- 2019-030 · 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
- 80
- effective_loc
- 7,579
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 6,565
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 49.03
- measured_loc
- 1,014
- median_loc_per_hour
- 21.39
- pr_timed_units
- 1
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 1,014
- work_units
- 19
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 39.80
- releases
- 4
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0
- lines_scanned
- 7,090
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
49 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 14% of function code in complex or long functions; 11% duplicated lines. Weakest area: testing.
How the score is built
- Complexity65
- Duplication53
- Lint and smells75
- Tests and CI15
- Documentation65
- Type safety40
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok7 items
- GTPExecute in mcts/mcts_main.cc: complexity 33, 135 lines
- main in configure.py: complexity 25, 120 lines
- set_tf_nccl_install_path in configure.py: complexity 20, 95 lines
- GoState::Move in common/go_state.cc: complexity 17, 79 lines
- set_tf_tensorrt_install_path in configure.py: complexity 17, 71 lines
- set_tf_cuda_version in configure.py: complexity 16, 52 lines
- MCTSEngine::GetBestMove in mcts/mcts_engine.cc: complexity 16, 53 lines
- complex_functions
- 7
- function_nloc
- 4,211
- functions
- 337
- long_functions
- 2
- many_param_functions
- 1
- mean_ccn
- 3.10
- p90_ccn
- 8
- risky_nloc_share
- 14.4%
Duplication (jscpd)ok7 items
- 6+ duplicated lines: common/errordef.h:2 and common/go_comm.cc:2
- 6+ duplicated lines: common/errordef.h:12 and common/go_comm.h:12
- 6+ duplicated lines: configure.py:274 and configure.py:392
- 6+ duplicated lines: mcts/debug_tool.cc:51 and mcts/mcts_engine.cc:1072
- 6+ duplicated lines: model/build_tensorrt_model.cc:12 and model/trt_zero_model.cc:12
- 6+ duplicated lines: model/checkpoint_utils.cc:12 and model/zero_model.cc:12
- 6+ duplicated lines: model/trt_zero_model.h:37 and model/zero_model.h:33
- compared_lines
- 4,783
- duplicated_lines
- 510
- duplicated_share
- 10.7%
- files
- 39
Lintok
- category:best-practice
- 6
- category:correctness
- 6
- findings
- 12
- scanned_lines
- 7,090
- weighted_findings
- 8.25
Tests and CIok1 item
- CI config: .travis.yml
.travis.yml
- check:ci_present
- yes
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- no
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 1
- cochange_commits
- 29
- cochange_share
- 0.0%
- source_lines
- 7,090
- test_lines
- 0
- test_ratio
- 0
Documentationok2 items
- README.md
README.md - LICENSE.TXT
LICENSE.TXT
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 211
Type safetyok
- check:low_escape_density
- yes
- check:strict_config
- no
- escapes
- 0
- escapes_per_kloc
- 0
Security
78 adequate
Security posture is adequate: 2 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)90
- 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
- 5
- findings_high
- 2
- findings_low
- 0
- findings_medium
- 3
- parse_errors
- 2
- scanned_lines
- 7,090
- 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
- 21.2%
- unpinned_manifests
- 0
Release downloadsok6 items
- release win-x64-gpu-v1 ships PhoenixGo-win-x64-gpu-v1.zip (15875 downloads)
- release win-x64-gpu-v1 ships PhoenixGo-win-x64-gpu-with-cuda-v1.zip (4361 downloads)
- release win-x64-cpuonly-v1 ships PhoenixGo-win-x64-cpuonly-v1.zip (15430 downloads)
- release PhoenixGo-mac-x64-cpuonly-v1.1 ships PhoenixGo-mac-x64-cpuonly-v1.1-noavx2-nofma.tgz (501 downloads)
- release PhoenixGo-mac-x64-cpuonly-v1.1 ships PhoenixGo-mac-x64-cpuonly-v1.1.tgz (764 downloads)
- links directly to a downloadable archive or installer
README.md
- binary_assets
- 7
- signals
- 2
- suspicious
- 0
Findings
2 high10 medium5 low
17 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
configure.py:143 | Detected subprocess function 'check_output' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
configure.py:147 | Detected subprocess function 'check_output' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an... | Static analysis (opengrep) |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
configure.py:124 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
configure.py:127 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
configure.py:132 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.correctness.common-mistakes.string-concat-in-list |
configure.py:170 | Detected strings that are implicitly concatenated inside a list. Python will implicitly concatenate strings when not explicitly delimited. Was this supposed to be individual elements of the list? | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
configure.py:249 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
configure.py:257 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
configure.py:756 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/c.lang.security.insecure-use-memset |
common/go_state.h:119 | 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 |
common/go_state.h:120 | 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 |
common/go_state.h:121 | 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) |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
scripts/build_tensorrt_model.sh:18 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
scripts/build_tensorrt_model.sh:24 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
scripts/build_tensorrt_model.sh:26 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
scripts/build_tensorrt_model.sh:6 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
scripts/start.sh:3 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
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 | ok | prov-4 | 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 | 12 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 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 | 5 | |
| 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 | fbf67f9aec42 | prov-5+qual-2+sec-2 | 0% | 49 | 78 |
| 2026-11-14 | fbf67f9aec42 | prov-4+qual-2+sec-2 | 0% | 49 | 78 |
Full text report
- Repository: https://github.com/Tencent/PhoenixGo
- Commit:
fbf67f9aec42531bff9569c44b85eb4c3f37b7be - Generated: 2026-11-14T14:52:01+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 | 60% | 100% |
| Code quality | 49 | poor | 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%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2018-05 | 6,777 | 0% |
| 2018-06 | 102 | 0% |
| 2018-08 | 49 | 0% |
| 2018-12 | 170 | 0% |
| 2019-02 | 481 | 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; 14% of function code in complex or long functions; 11% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 65 |
| Duplication | 53 |
| Code smells (Opengrep) | 75 |
| Tests and CI | 15 |
| Documentation | 65 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 337; mean complexity 3.1, 90th percentile 8; 7 complex and 2 long functions
- Duplicated lines: 10.7% of 4,783 compared
- Tests: 0 test lines for 7,090 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- GTPExecute in mcts/mcts_main.cc: complexity 33, 135 lines
- main in configure.py: complexity 25, 120 lines
- set_tf_nccl_install_path in configure.py: complexity 20, 95 lines
- GoState::Move in common/go_state.cc: complexity 17, 79 lines
- set_tf_tensorrt_install_path in configure.py: complexity 17, 71 lines
Security
Security posture is adequate: 2 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 90 |
| 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 |
|---|---|---|
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'check_output' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
configure.py:143 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'check_output' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
configure.py:147 |
| 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] |
common/go_state.h:119 |
| 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] |
common/go_state.h:120 |
| 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] |
common/go_state.h:121 |
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.
Distribution signals
- binary-release-asset: release win-x64-gpu-v1 ships PhoenixGo-win-x64-gpu-v1.zip (15875 downloads)
- binary-release-asset: release win-x64-gpu-v1 ships PhoenixGo-win-x64-gpu-with-cuda-v1.zip (4361 downloads)
- binary-release-asset: release win-x64-cpuonly-v1 ships PhoenixGo-win-x64-cpuonly-v1.zip (15430 downloads)
- binary-release-asset: release PhoenixGo-mac-x64-cpuonly-v1.1 ships PhoenixGo-mac-x64-cpuonly-v1.1-noavx2-nofma.tgz (501 downloads)
- binary-release-asset: release PhoenixGo-mac-x64-cpuonly-v1.1 ships PhoenixGo-mac-x64-cpuonly-v1.1.tgz (764 downloads)
- readme-download-lure: links directly to a downloadable archive or installer
Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.
Repository profile
- Source lines: 7,090; test lines: 0
| Language | Lines |
|---|---|
| C++ | 3,722 |
| Python | 1,747 |
| C | 1,540 |
| Shell | 81 |