RepoTrust

Leaderboard github.com

shadowsocksr-backup/shadowsocksr-csharp

  • View repository ↗
  • C#
  • ★ 4,472
  • commit 932b86ef5783
  • scored 2026-11-14
  • scoring prov-5+qual-2+sec-2

AI provenance

0%

none-detected

Confidence
65%
Coverage
100%

Estimated share of AI-generated code. Explicit attribution is a lower bound.

Code quality

55/100

weak

Confidence
90%
Coverage
100%

Complexity, duplication, lint density, tests, CI, docs and review process.

Security

80/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.13

Lines added per month all AI-attributed share

  1. 2013-011,302 · 0% AI
  2. 2013-030 · 0% AI
  3. 2013-05249 · 0% AI
  4. 2013-06239 · 0% AI
  5. 2014-09421 · 0% AI
  6. 2014-119,042 · 0% AI
  7. 2014-126,082 · 0% AI
  8. 2015-0114,819 · 0% AI
  9. 2015-0220 · 0% AI
  10. 2015-03498 · 0% AI
  11. 2015-040 · 0% AI
  12. 2015-060 · 0% AI
  13. 2015-07459 · 0% AI
  14. 2015-087,498 · 0% AI
  15. 2015-091,699 · 0% AI
  16. 2015-101,815 · 0% AI
  17. 2015-111,858 · 0% AI
  18. 2015-121,630 · 0% AI
  19. 2016-011,787 · 0% AI
  20. 2016-0251 · 0% AI
  21. 2016-03620 · 0% AI
  22. 2016-041,234 · 0% AI
  23. 2016-051,227 · 0% AI
  24. 2016-061,865 · 0% AI
  25. 2016-084,472 · 0% AI
  26. 2016-092,525 · 0% AI
  27. 2016-102,599 · 0% AI
  28. 2016-123,465 · 0% AI
  29. 2017-011,387 · 0% AI
  30. 2017-02709 · 0% AI
  31. 2017-03684 · 0% AI
  32. 2017-041,293 · 0% AI
  33. 2017-051,135 · 0% AI
  34. 2017-061,914 · 0% AI
  35. 2017-07294 · 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
702
effective_loc
74,892
tools_detected
0
AI tool configurationok
artifacts
0
tools_configured
0
workflow_agents
0
Commit velocityok
excluded_import_loc
7,418
flagged_loc
0
flagged_loc_share
0.0%
flagged_units
0
max_loc_per_hour
1,765.67
measured_loc
67,474
median_loc_per_hour
75
pr_timed_units
0
pre_ai_era_burst_loc
20,586
pre_ai_era_bursts
7
pre_ai_era_measured_loc
67,474
work_units
324
Release velocityok
flagged_releases
0
max_loc_per_day
3,587.20
releases
79
Coding styleok5 items
count:assistant_voice
0
count:emoji_in_code
0
count:narrated_steps
5
count:placeholder
0
files:assistant_voice
0
files:emoji_in_code
0
files:narrated_steps
3
files:placeholder
0
index
0.13
lines_scanned
39,296
per_kloc:assistant_voice
0
per_kloc:emoji_in_code
0
per_kloc:narrated_steps
0.13
per_kloc:placeholder
0

Code quality

55 weak

Code quality is weak: test-to-source ratio 0.01, no CI test run detected; 26% of function code in complex or long functions; 12% duplicated lines. Weakest area: testing.

How the score is built

  • Complexity45
  • Duplication49
  • Lint and smells99
  • Tests and CI20
  • Documentation100
  • Type safetynot measured
  • Review processnot measured

Evidence by analyzer

Complexity (lizard)ok10 items
complex_functions
41
function_nloc
25,843
functions
1,325
long_functions
26
many_param_functions
7
mean_ccn
3.73
p90_ccn
8
risky_nloc_share
26.3%
Duplication (jscpd)ok10 items
compared_lines
24,279
duplicated_lines
2,867
duplicated_share
11.8%
files
136
Lintok
category:best-practice
3
category:correctness
2
findings
5
scanned_lines
39,296
weighted_findings
1.25
Tests and CIok
check:ci_present
no
check:ci_runs_lint
no
check:ci_runs_tests
no
check:has_tests
yes
check:test_ratio
no
check:tests_cochange
no
ci_files
0
cochange_commits
284
cochange_share
0.4%
source_lines
39,296
test_lines
215
test_ratio
0.01
Documentationok4 items
  • README.md README.md
  • LICENSE LICENSE
  • CONTRIBUTING.md CONTRIBUTING.md
  • CHANGES CHANGES
check:changelog
yes
check:contributing
yes
check:license
yes
check:readme
yes
readme_lines
50
Type safetyskipped

Security

80 adequate

Security posture is adequate: no high-impact findings. Weakest area: posture.

How the score is built

  • Secrets97
  • Static analysis (SAST)100
  • 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
1
secrets_nonprod
0
Static analysis (opengrep)ok
findings
0
findings_high
0
findings_low
0
findings_medium
0
parse_errors
3
scanned_lines
39,296
weighted_findings
0
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 downloadsok1 item
binary_assets
1
signals
1
suspicious
0

Findings

6 low

SeverityRuleLocationMessageTool
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command packaging/upload.sh:5 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 packaging/upload.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/csharp.lang.best-practice.structured-logging shadowsocks-csharp/Controller/Local.cs:754 String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... Lint
low opengrep/csharp.lang.best-practice.structured-logging shadowsocks-csharp/Controller/Local.cs:757 String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... Lint
low opengrep/csharp.lang.best-practice.structured-logging shadowsocks-csharp/Controller/Local.cs:838 String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... Lint
low gitleaks/generic-api-key shadowsocks-csharp/View/HotkeySettingsForm.cs:119 Possible generic-api-key secret in history (commit 99bdec334c); removed from the current tree but still retrievable Secrets (gitleaks)

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.

AnalyzerPillarStatusVersionFindingsNote
AI tool configurationAI provenanceoksignatures-v10
Explicit AI attributionAI provenanceoksignatures-v10
Release velocityAI provenanceokprov-40
Coding styleAI provenanceok—0
Commit velocityAI provenanceokprov-40
Complexity (lizard)Code qualityoklizard 1.25.10
DocumentationCode qualityok—0
Duplication (jscpd)Code qualityokrepotrust-dup-w60
LintCode qualityokopengrep 1.33.1; rules f1d2b562b4145
Tests and CICode qualityok—0
Type safetyCode qualityskipped—0
CI workflows (zizmor)Securityskipped—0
Dependencies (osv-scanner)Securityskipped—0
Release downloadsSecurityok—0
Security postureSecurityok—0
Package registriesSecurityskipped—0no registry dependencies declared
Static analysis (opengrep)Securityokopengrep 1.33.1; rules f1d2b562b4140
OpenSSF ScorecardSecurityskipped—0no published OpenSSF Scorecard result for this repo
Secrets (gitleaks)Securityokgitleaks 8.30.11

Score history

Scores from different scoring versions aren't directly comparable.

ScoredCommitScoringAI provenanceQualitySecurity
2026-11-14932b86ef5783prov-5+qual-2+sec-20%5580
2026-11-14932b86ef5783prov-4+qual-2+sec-20%5580

Embed a badge

Maintainers can show these in a README. Badges update when the repository is re-scored.

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/shadowsocksr-backup/shadowsocksr-csharp/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/shadowsocksr-backup/shadowsocksr-csharp/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/shadowsocksr-backup/shadowsocksr-csharp/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/shadowsocksr-backup/shadowsocksr-csharp/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/shadowsocksr-backup/shadowsocksr-csharp/security.svg)](https://repotrust.synapticcyber.com/r/github.com/shadowsocksr-backup/shadowsocksr-csharp/)
Full text report

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 0 none-detected 65% 100%
Code quality 55 weak 90% 100%
Security 80 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.13 per 1,000 lines (narrated steps 5, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.

Month Lines added Attributed to AI
2016-06 1,865 0%
2016-08 4,472 0%
2016-09 2,525 0%
2016-10 2,599 0%
2016-12 3,465 0%
2017-01 1,387 0%
2017-02 709 0%
2017-03 684 0%
2017-04 1,293 0%
2017-05 1,135 0%
2017-06 1,914 0%
2017-07 294 0%

Evidence

  • step-by-step narration comment: // First, read remainder from current byte (shadowsocks-)
  • step-by-step narration comment: // Step 1. Divide data bytes into blocks and generate error correction bytes for them. We'll (shadowsocks-)
  • step-by-step narration comment: // First, place data blocks. (shadowsocks-)
  • step-by-step narration comment: // Then, place error correction blocks. (shadowsocks-)
  • step-by-step narration comment: // Then, embed the dark dot at the left bottom corner. (shadowsocks-)

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.01, no CI test run detected; 26% of function code in complex or long functions; 12% duplicated lines. Weakest area: testing.

Area Score
Complexity (lizard) 45
Duplication 49
Code smells (Opengrep) 99
Tests and CI 20
Documentation 100
Type safety n/a
Process (Scorecard review/maintenance) n/a
  • Functions: 1,325; mean complexity 3.7, 90th percentile 8; 41 complex and 26 long functions
  • Duplicated lines: 11.8% of 24,279 compared
  • Tests: 215 test lines for 39,296 source lines (ratio 0.01); CI test commands: none detected; 0% of recent source commits also change tests
  • Docs missing or thin: none

Most complex functions:

Security

Security posture is adequate: no high-impact findings. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 97
Static analysis (Opengrep) 100
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
low gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 99bdec334c); removed from the current tree but still retrievable shadowsocks-csharp/View/HotkeySettingsForm.cs:119

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

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: 39,296; test lines: 215
Language Lines
C# 39,505
Shell 6