Leaderboard github.com

Terry-Mao/gopush-cluster

Golang push server cluster

View repository ↗
Go
★ 2,066
commit 1c279b4d085f
scored 2026-11-14
scoring prov-5+qual-2+sec-2

AI provenance

none-detected

Confidence: 65%
Coverage: 100%

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

Code quality

53/100

weak

Confidence: 90%
Coverage: 100%

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

Security

66/100

weak

Confidence: 85%
Coverage: 100%

Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.

Dispute or request a re-score Full report JSON

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

2013-123,739 · 0% AI
2014-015,012 · 0% AI
2014-02518 · 0% AI
2014-032,473 · 0% AI
2014-043,420 · 0% AI
2014-0589 · 0% AI
2014-06440 · 0% AI
2014-08886 · 0% AI
2014-092,069 · 0% AI
2014-1095 · 0% AI
2014-123 · 0% AI
2015-011 · 0% AI
2015-0915 · 0% AI
2016-013 · 0% AI
2016-0636 · 0% AI
2016-083 · 0% AI
2016-1217 · 0% AI
2017-0440 · 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: 485
effective_loc: 18,859
tools_detected: 0

AI tool configurationok

artifacts: 0
tools_configured: 0
workflow_agents: 0

Commit velocityok

excluded_import_loc: 0
flagged_loc: 0
flagged_loc_share: 0.0%
flagged_units: 0
max_loc_per_hour: 309.68
measured_loc: 18,859
median_loc_per_hour: 59.75
pr_timed_units: 0
pre_ai_era_burst_loc: 0
pre_ai_era_bursts: 0
pre_ai_era_measured_loc: 18,859
work_units: 210

Release velocityok

flagged_releases: 0
max_loc_per_day: 308.70
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: 6,278
per_kloc:assistant_voice: 0
per_kloc:emoji_in_code: 0
per_kloc:narrated_steps: 0
per_kloc:placeholder: 0

Code quality

53 weak

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

How the score is built

Complexity77
Duplication28
Lint and smells67
Tests and CI28
Documentation85
Type safetynot measured
Review processnot measured

Evidence by analyzer

Complexity (lizard)ok3 items

complex_functions: 3
function_nloc: 3,622
functions: 236
long_functions: 1
many_param_functions: 0
mean_ccn: 3.39
p90_ccn: 7
risky_nloc_share: 8.7%

Duplication (jscpd)ok10 items

compared_lines: 4,714
duplicated_lines: 989
duplicated_share: 21.0%
files: 48

Lintok

category:best-practice: 1
category:correctness: 12
findings: 13
scanned_lines: 6,227
weighted_findings: 10

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: 225
cochange_share: 5.8%
source_lines: 6,278
test_lines: 647
test_ratio: 0.10

Documentationok3 items

README.md README.md
LICENSE LICENSE
CHANGELOG.md CHANGELOG.md

check:changelog: yes
check:contributing: no
check:license: yes
check:readme: yes
readme_lines: 24

Type safetyskipped

Security

66 weak

Security posture is weak: 3 high-severity SAST findings. Weakest area: posture.

How the score is built

Secrets100
Static analysis (SAST)58
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: 12
findings_high: 3
findings_low: 0
findings_medium: 9
parse_errors: 0
scanned_lines: 6,227
weighted_findings: 9.75

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

3 high18 medium4 low

Severity	Rule	Location	Message	Tool
high	`opengrep/dockerfile.security.missing-user`	comet/Dockerfile:25	By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile...	Static analysis (opengrep)
high	`opengrep/dockerfile.security.missing-user`	message/Dockerfile:24	By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile...	Static analysis (opengrep)
high	`opengrep/dockerfile.security.missing-user`	web/Dockerfile:24	By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile...	Static analysis (opengrep)
medium	`opengrep/go.lang.best-practice.hidden-goroutine`	comet/conn.go:34	Detected a hidden goroutine. Function invocations are expected to synchronous, and this function will execute asynchronously because all it does is call a goroutine. Instead, remove the internal goroutine and call the function using 'go'.	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	process/process.go:42	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	rpc/comet.go:149	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	rpc/comet.go:271	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	rpc/comet.go:307	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	rpc/message.go:160	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	rpc/message.go:162	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	zk/zk.go:61	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	zk/zk.go:79	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.security.audit.net.use-tls`	comet/pubsub_websocket.go:78	Found an HTTP server without TLS. Use 'http.ListenAndServeTLS' instead. See https://golang.org/pkg/net/http/#ListenAndServeTLS for more information. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.net.use-tls`	comet/stat.go:119	Found an HTTP server without TLS. Use 'http.ListenAndServeTLS' instead. See https://golang.org/pkg/net/http/#ListenAndServeTLS for more information. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	comet/stat.go:276	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`	ketama/ketama.go:67	Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`	ketama/ketama.go:88	Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.net.use-tls`	perf/perf.go:34	Found an HTTP server without TLS. Use 'http.ListenAndServeTLS' instead. See https://golang.org/pkg/net/http/#ListenAndServeTLS for more information. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`	rpc/rand_lb.go:23	Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	web/http.go:109	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	web/http.go:92	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
low	`opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command`	spawn-docker-images.sh:21	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`	spawn-docker-images.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
low	`opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command`	spawn-docker-images.sh:33	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`	spawn-docker-images.sh:8	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`	13
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`	12
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	`1c279b4d085f`	`prov-5+qual-2+sec-2`	0%	53	66
2026-11-14	`1c279b4d085f`	`prov-4+qual-2+sec-2`	0%	53	66

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/Terry-Mao/gopush-cluster/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/Terry-Mao/gopush-cluster/)

[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/Terry-Mao/gopush-cluster/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/Terry-Mao/gopush-cluster/)

[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/Terry-Mao/gopush-cluster/security.svg)](https://repotrust.synapticcyber.com/r/github.com/Terry-Mao/gopush-cluster/)

Full text report

Repository: https://github.com/Terry-Mao/gopush-cluster
Commit: 1c279b4d085fe66fc0cfca66bf2ddfeb0a5d3bc5
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	65%	100%
Code quality	53	weak	90%	100%
Security	66	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%

Month	Lines added	Attributed to AI
2014-06	440	0%
2014-08	886	0%
2014-09	2,069	0%
2014-10	95	0%
2014-12	3	0%
2015-01	1	0%
2015-09	15	0%
2016-01	3	0%
2016-06	36	0%
2016-08	3	0%
2016-12	17	0%
2017-04	40	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.10, no CI test run detected; 9% of function code in complex or long functions; 21% duplicated lines. Weakest area: testing.

Area	Score
Complexity (lizard)	77
Duplication	28
Code smells (Opengrep)	67
Tests and CI	28
Documentation	85
Type safety	n/a
Process (Scorecard review/maintenance)	n/a

Functions: 236; mean complexity 3.4, 90th percentile 7; 3 complex and 1 long functions
Duplicated lines: 21.0% of 4,714 compared
Tests: 647 test lines for 6,278 source lines (ratio 0.10); CI test commands: none detected; 6% of recent source commits also change tests
Docs missing or thin: contributing

Most complex functions:

Security

Security posture is weak: 3 high-severity SAST findings. Weakest area: posture.

Area	Score
Secrets (gitleaks, tree + history)	100
Static analysis (Opengrep)	58
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/dockerfile.security.missing-user`: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium]	comet/Dockerfile:25
high	`opengrep/dockerfile.security.missing-user`: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium]	message/Dockerfile:24
high	`opengrep/dockerfile.security.missing-user`: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium]	web/Dockerfile:24
medium	`opengrep/go.lang.security.audit.net.use-tls`: Found an HTTP server without TLS. Use 'http.ListenAndServeTLS' instead. See https://golang.org/pkg/net/http/#ListenAndServeTLS for more information. [confidence medium]	comet/pubsub_websocket.go:78
medium	`opengrep/go.lang.security.audit.net.use-tls`: Found an HTTP server without TLS. Use 'http.ListenAndServeTLS' instead. See https://golang.org/pkg/net/http/#ListenAndServeTLS for more information. [confidence medium]	comet/stat.go:119
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`: Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. [confidence low]	comet/stat.go:276
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`: Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	ketama/ketama.go:67
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`: Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	ketama/ketama.go:88
medium	`opengrep/go.lang.security.audit.net.use-tls`: Found an HTTP server without TLS. Use 'http.ListenAndServeTLS' instead. See https://golang.org/pkg/net/http/#ListenAndServeTLS for more information. [confidence medium]	perf/perf.go:34
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`: Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	rpc/rand_lb.go:23
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`: Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. [confidence low]	web/http.go:92
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`: Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. [confidence low]	web/http.go:109

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: 6,278; test lines: 647

Language	Lines
Go	6,820
Shell	54
SQL	51