Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 16:05 UTC

NordSecurity / quic-go

A production-ready QUIC implementation in pure Go

GoMIT★ 0 stars⑂ 1 forksince Dec 2025forkView on GitHub ↗

NordSecurity/quic-go holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on AI Readiness (76/100) and lowest on Community & Adoption (12/100). It was last updated 35 days ago. A single contributor accounts for most of its recent work.

44
overall / 100
Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

44
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 46 is calibrated to 44 on the published index scale (record calibration 2026-08-02).

Ownership

Nord SecurityOrganization · verified domain
408 followers60 public repossince Oct 2020

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/quic-go/quic-gopoints to another repo — not scoredv0.61.0-12938 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

52Moderate · 21% of overall
How it's scored
18/36Push recencylast push 35 days ago
9/36Commit cadence13/52 weeks with commits
17.8/18Commit volume96 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year96
human_commit_share0.96
days_since_last_push35
active_weeks_last_year13
How it's scored
27/27Ships releases1 releases published
16.2/36Release recencylatest release 263 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv0.52.0
releases_from_tagsno
days_since_latest_release263
mean_days_between_releases
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

12Critical · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges20
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicespkg.go.dev, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

43Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.4/22.5Commit distributiontop contributor authored 85% of commits
13.5/13.5Contributor breadth98 contributors
10/10OpenSSF Scorecard: Contributorsproject has 14 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled98
top_contributor_share0.851
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptance0/1 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
18.8/25Owner reach408 followers of NordSecurity
24.7/25Track record60 public repos, account ~5 yr old
Inputs used
followers408
owner_typeOrganization
is_verifiedyes
owner_loginNordSecurity
public_repos60
account_age_days2,138

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://quic-go.net
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://quic-go.net
docs_sitehttps://quic-go.net
has_readmeno
has_docs_diryes
has_descriptionno

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 14 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0/5SASTno SAST tool detected
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities32 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
5.7/35Direct dependencies free of known advisories3 affected: golang.org/x/crypto 0.41.0 (critical 10.0), golang.org/x/net 0.43.0 (moderate 6.5), golang.org/x/sys 0.35.0 (unknown)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
26.9/40No advisories left outstanding3 advisory-carrying package(s) unaddressed past 90 days; oldest published 287 days ago
Inputs used
sourceosv
advisories48
affected_packages5
assessed_packages17
unassessed_packages0
affected_by_severitycritical 1, moderate 1, unknown 3
direct_affected_packages3
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 17 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

76Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history96 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapgo.mod, integrationtests/gomodvendor/go.mod (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.golangci.yml
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice5 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance4 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.05
toolchain_manifestsgo.mod, integrationtests/gomodvendor/go.mod
dependency_bot_commit_share0.04
How it's scored
45/45Type-checkable codeGo (statically typed)
54.8/55Manageable file sizes2/442 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes115,752
source_files_sampled442
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
98contributors
96commits, last 12 months
35days since last push
1releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

  • Community profile unavailable
  • go package 'github.com/quic-go/quic-go' points at a different repository (https://github.com/quic-go/quic-go); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 4.5 / 10
4.5aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-28 16:05 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 14 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities32 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
Gogithub.com/quic-go/qpackv0.6.0go.mod
Gogithub.com/stretchr/testifyv1.11.1go.mod
Gogo.uber.org/mockv0.5.2go.mod
Gogolang.org/x/cryptov0.41.0go.mod
Gogolang.org/x/netv0.43.0go.mod
Gogolang.org/x/syncv0.16.0go.mod
Gogolang.org/x/sysv0.35.0go.mod
Gogithub.com/quic-go/quic-gov0.21.0integrationtests/gomodvendor/go.mod
All dependencies 17

Full resolved dependency set from the GitHub dependency graph: 7 direct and 10 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Gogithub.com/quic-go/qpack0.6.0direct
Gogithub.com/stretchr/testify1.11.1direct
Gogo.uber.org/mock0.5.2direct
Gogolang.org/x/crypto0.41.0direct
Gogolang.org/x/net0.43.0direct
Gogolang.org/x/sync0.16.0direct
Gogolang.org/x/sys0.35.0direct
Gogithub.com/davecgh/go-spew1.1.1indirect
Gogithub.com/jordanlewis/gcassert0.0.0-20250430164644-389ef753e22eindirect
Gogithub.com/kr/pretty0.3.1indirect
Gogithub.com/pmezard/go-difflib1.0.0indirect
Gogithub.com/rogpeppe/go-internal1.10.0indirect
Gogolang.org/x/mod0.27.0indirect
Gogolang.org/x/text0.28.0indirect
Gogolang.org/x/tools0.36.0indirect
Gogopkg.in/check.v11.0.0-20201130134442-10cb98267c6cindirect
Gogopkg.in/yaml.v33.0.1indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 17 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 3 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/crypto0.41.0directcritical330.55.0
golang.org/x/net0.43.0directmoderate111.27.0-rc.3
golang.org/x/sys0.35.0directunknown10.44.0
golang.org/x/mod0.27.0indirectunknown21.27.0-rc.3
golang.org/x/text0.28.0indirectunknown10.39.0

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo.