RepoTrust

Leaderboard github.com

lanceylai/TSWeChat

A WeChat alternative. Written in Swift 5.

  • View repository ↗
  • Swift
  • ★ 3,743
  • commit a1d371a7b25e
  • scored 2026-11-14
  • scoring prov-5+qual-2+sec-2

AI provenance

0%

none-detected

Confidence
52%
Coverage
100%

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

Code quality

61/100

weak

Confidence
90%
Coverage
100%

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

Security

59/100

weak

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.46

Lines added per month all AI-attributed share

  1. 2016-024,937 · 0% AI
  2. 2016-036,990 · 0% AI
  3. 2016-040 · 0% AI
  4. 2016-0853 · 0% AI
  5. 2016-093 · 0% AI
  6. 2016-111,625 · 0% AI
  7. 2017-032 · 0% AI
  8. 2018-03172 · 0% AI
  9. 2018-0418 · 0% AI
  10. 2019-021 · 0% AI
  11. 2019-07139 · 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
49
effective_loc
13,940
tools_detected
0
AI tool configurationok
artifacts
0
tools_configured
0
workflow_agents
0
Commit velocityok
excluded_import_loc
10,808
flagged_loc
0
flagged_loc_share
0.0%
flagged_units
0
max_loc_per_hour
341.25
measured_loc
3,132
median_loc_per_hour
52.43
pr_timed_units
3
pre_ai_era_burst_loc
0
pre_ai_era_bursts
0
pre_ai_era_measured_loc
3,132
work_units
27
Release velocityskipped
Coding styleok
count:assistant_voice
0
count:emoji_in_code
8
count:narrated_steps
0
count:placeholder
0
files:assistant_voice
0
files:emoji_in_code
1
files:narrated_steps
0
files:placeholder
0
index
0.46
lines_scanned
8,675
per_kloc:assistant_voice
0
per_kloc:emoji_in_code
0.92
per_kloc:narrated_steps
0
per_kloc:placeholder
0

Code quality

61 weak

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

How the score is built

  • Complexity96
  • Duplication81
  • Lint and smells93
  • Tests and CI0
  • Documentation65
  • Type safetynot measured
  • Review processnot measured

Evidence by analyzer

Complexity (lizard)ok1 item
complex_functions
1
function_nloc
4,240
functions
510
long_functions
0
many_param_functions
0
mean_ccn
1.88
p90_ccn
4
risky_nloc_share
1.4%
Duplication (jscpd)ok10 items
compared_lines
5,453
duplicated_lines
193
duplicated_share
3.5%
files
90
Lintok
category:correctness
10
findings
10
scanned_lines
8,675
weighted_findings
2.50
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
32
cochange_share
0.0%
source_lines
8,675
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
yes
readme_lines
57
Type safetyskipped

Security

59 weak

Security posture is weak: 1 possible secret(s) in the tree, 1 only in history. Weakest area: posture.

How the score is built

  • Secrets49
  • 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
1
secrets_history
1
secrets_low_confidence
4
secrets_nonprod
0
Static analysis (opengrep)ok
findings
0
findings_high
0
findings_low
0
findings_medium
0
parse_errors
67
scanned_lines
8,675
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
2.0%
unpinned_manifests
0
Release downloadsok
binary_assets
0
signals
0
suspicious
0

Findings

1 high1 medium14 low

SeverityRuleLocationMessageTool
high gitleaks/square-access-token Pods/Pods.xcodeproj/project.pbxproj:779 Possible square-access-token secret in the current tree Secrets (gitleaks)
medium gitleaks/square-access-token Pods/Pods.xcodeproj/xcshareddata/xcschemes/Alamofire.xcscheme:17 Possible square-access-token secret in history (commit f73704814f); removed from the current tree but still retrievable Secrets (gitleaks)
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Scripts/xcodebuild.sh:103 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/xcodebuild.sh:104 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/xcodebuild.sh:106 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/xcodebuild.sh:107 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-command-substitution-in-command Scripts/xcodebuild.sh:115 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Scripts/xcodebuild.sh:115 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/xcodebuild.sh:120 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/xcodebuild.sh:59 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/xcodebuild.sh:62 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/xcodebuild.sh:66 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 gitleaks/generic-api-key Podfile.lock:96 Possible generic-api-key secret in the current tree Secrets (gitleaks)
low gitleaks/generic-api-key Pods/Manifest.lock:96 Possible generic-api-key secret in the current tree Secrets (gitleaks)
low gitleaks/generic-api-key Scripts/apns.php:5 Possible generic-api-key secret in the current tree Secrets (gitleaks)
low gitleaks/generic-api-key TSWeChat/Resources/JSON/chat.json:52 Possible generic-api-key secret in the current tree 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 provenanceskipped—0
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 f1d2b562b41410
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.16

Score history

Scores from different scoring versions aren't directly comparable.

ScoredCommitScoringAI provenanceQualitySecurity
2026-11-14a1d371a7b25eprov-5+qual-2+sec-20%6159
2026-11-14a1d371a7b25eprov-4+qual-2+sec-20%6159

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/lanceylai/TSWeChat/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/lanceylai/TSWeChat/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/lanceylai/TSWeChat/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/lanceylai/TSWeChat/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/lanceylai/TSWeChat/security.svg)](https://repotrust.synapticcyber.com/r/github.com/lanceylai/TSWeChat/)
Full text report
  • Repository: https://github.com/lanceylai/TSWeChat
  • Commit: a1d371a7b25e8e8eea8747e37289cd3386516602
  • Generated: 2026-11-14T14:52:06+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 52% 100%
Code quality 61 weak 90% 100%
Security 59 weak 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.46 per 1,000 lines (narrated steps 0, placeholders 0, assistant phrasing 0, emoji 8). Reported as a signal, not scored.

Month Lines added Attributed to AI
2016-02 4,937 0%
2016-03 6,990 0%
2016-08 53 0%
2016-09 3 0%
2016-11 1,625 0%
2017-03 2 0%
2018-03 172 0%
2018-04 18 0%
2019-02 1 0%
2019-07 139 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 weak: test-to-source ratio 0.00, no CI test run detected; 1% of function code in complex or long functions; 4% duplicated lines. Weakest area: testing.

Area Score
Complexity (lizard) 96
Duplication 81
Code smells (Opengrep) 93
Tests and CI 0
Documentation 65
Type safety n/a
Process (Scorecard review/maintenance) n/a
  • Functions: 510; mean complexity 1.9, 90th percentile 4; 1 complex and 0 long functions
  • Duplicated lines: 3.5% of 5,453 compared
  • Tests: 0 test lines for 8,675 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:

Security

Security posture is weak: 1 possible secret(s) in the tree, 1 only in history. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 49
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
high gitleaks/square-access-token: Possible square-access-token secret in the current tree Pods/Pods.xcodeproj/project.pbxproj:779
medium gitleaks/square-access-token: Possible square-access-token secret in history (commit f73704814f); removed from the current tree but still retrievable Pods/Pods.xcodeproj/xcshareddata/xcschemes/Alamofire.xcscheme:17
low gitleaks/generic-api-key: Possible generic-api-key secret in the current tree Pods/Manifest.lock:96
low gitleaks/generic-api-key: Possible generic-api-key secret in the current tree Podfile.lock:96
low gitleaks/generic-api-key: Possible generic-api-key secret in the current tree Scripts/apns.php:5
low gitleaks/generic-api-key: Possible generic-api-key secret in the current tree TSWeChat/Resources/JSON/chat.json: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: 8,675; test lines: 0
Language Lines
Swift 8,468
Shell 129
PHP 66
C 12