--
Static Analysis Breakdown
5 core automated checks evaluated by goreport-cli
Loading Report...
Report Not Found
We couldn't locate a generated analysis report for this module path.
Documentation
About goscore.dev
Standardized static analysis, code quality benchmarks, and vulnerability evaluation for the Go ecosystem.
Overview & Mission
goscore.dev was created to give Go developers and engineering teams instantaneous, reliable, and transparent static analysis scoring across the top open-source Go modules. By aggregating industry-standard tools into a unified metric, we help developers assess dependency health, security posture, and maintainability at a glance.
The 5 Core Analysis Pillars
🛠️
govet
Runs official go vet diagnostics to detect correctness defects, suspicious constructs, shadow variables, and unsafe concurrency patterns.
🔒
govulncheck
Leverages the Go Vulnerability Database to surface known public CVEs and vulnerable symbols actually reachable within your dependency graph.
✨
gofmt
Verifies Go canonical formatting compliance across all module source files to enforce clean, idiomatic formatting conventions.
🔄
gocyclo
Calculates cyclomatic complexity across all functions and methods to identify overly branched, hard-to-test code blocks.
📦
go mod verify
Validates cryptographic checksums of module dependencies recorded in go.sum against downloaded cache sources.
Scoring & Grading System
Each module receives an overall weighted score from 0 to 100 along with an intuitive letter grade:
A+ (95–100) Exceptional
A (90–94) Excellent
B (80–89) Good
C (70–79) Needs Work
D (60–69) Poor
F (<60) Failing
Architecture & Infrastructure
The goscore.dev backend pipeline continuously analyzes modules identified from public BigQuery datasets (bigquery-public-data.github_repos) using our dedicated CLI analyzer goreport-cli. Pre-computed reports are served via Cloudflare Workers and R2 object storage with fast, zero-latency client-side search powered by MiniSearch.
Get in Touch
Contact & Community
Have questions, feedback, or want to submit a Go module for scoring?
General Inquiries & Support
For general questions, metric feedback, scoring methodology inquiries, or team collaborations.
info@goscore.dev →Submit a Module
Want your public or open-source Go package indexed in the top benchmark dataset? Send your module path to our team.
Request Indexing →Email Inquiries & Module Submissions
For all questions, feedback, corrections, or requests to benchmark and index a Go module, please email us directly:
When submitting a module for indexing, please include the canonical Go module path (e.g. github.com/org/repo) and any specific version tags you would like scored.