Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 09:59 UTC

uber-go / zap

Blazing fast, structured, leveled logging in Go.

GoMIT★ 24,635 stars⑂ 1,548 forkssince Feb 2016View on GitHub ↗

uber-go/zap holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (92/100) and lowest on Vitality (55/100). It was last updated 16 days ago. 3 contributors account for most of its recent work.

88
overall / 100
Excellent

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.

88
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 74 is calibrated to 88 on the published index scale (record calibration 2026-08-02).

Ownership

Uber GoOrganization
2,591 followers26 public repossince May 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogo.uber.org/zapv1.28.0-40116 days ago
Gogo.uber.org/zap/expv0.3.0-3668 days ago

Metrics by category

Vitality

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

55Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 16 days ago
4.8/36Commit cadence7/52 weeks with commits
9/18Commit volume9 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year9
human_commit_share0.88
days_since_last_push16
active_weeks_last_year7
How it's scored
27/27Ships releases41 releases published
27/36Release recencylatest release 116 days ago
12.6/27Release cadencea release every ~171.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count41
latest_release_tagv1.28.0
releases_from_tagsno
days_since_latest_release116
mean_days_between_releases171.2
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?

92Excellent · 17% of overall
How it's scored
60/60Stars24,635 stars
25/25Forks1,548 forks
13.3/15Watchers246 watchers
Inputs used
forks1,548
stars24,635
watchers246
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

86Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
17.2/22.5Commit distributiontop contributor authored 24% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 13 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.235
How it's scored
34.2/42Issue resolution81% of issues closed
23.6/30PR acceptance577/734 decided PRs merged
4.3/13Newcomer PR acceptance1/3 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs577
open_issues123
closed_issues537
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d3
issue_closed_ratio0.814
closed_unmerged_prs157
first_time_authors_30d3
first_time_prs_merged_30d1
first_time_prs_decided_30d3
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
24.5/25Owner reach2,591 followers of uber-go
22.4/25Track record26 public repos, account ~10 yr old
Inputs used
followers2,591
owner_typeOrganization
is_verified
owner_loginuber-go
public_repos26
account_age_days3,757
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on go
35/35Publish recencylatest publish 116 days ago
20/20Version history40 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgo.uber.org/zap, go.uber.org/zap/exp
ecosystemsgo
any_deprecatedno
min_days_since_publish116

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests4 out of 30 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pkg.go.dev/go.uber.org/zap
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsgolang, logging, structured-logging, zap
has_wikino
homepagehttps://pkg.go.dev/go.uber.org/zap
docs_sitehttps://pkg.go.dev/go.uber.org/zap
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

71Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests4 out of 30 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 13 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.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
3.8/7.5Vulnerabilities5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories16
affected_packages6
assessed_packages44
unassessed_packages0
affected_by_severitycritical 2, high 1, unknown 3
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 44 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.

70Good · 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 history87 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.989
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.golangci.yml
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance12 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifestsassets/go.mod, benchmarks/go.mod, exp/go.mod, go.mod, tools/go.mod, zapgrpc/internal/test/go.mod
dependency_bot_commit_share0.12
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/143 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes29,144
source_files_sampled143
oversized_source_files0

Key facts

24,635GitHub stars
99contributors
9commits, last 12 months
16days since last push
41releases
3bus factor
123open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch go package 'go.uber.org/zap/tools' from its registry
  • Could not fetch go package 'go.uber.org/zap/assets' from its registry

More detail

Star and fork history 0 ★ / 1,548 ⇿
0Stars
1,548Forks
20Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

4006008001,0001,2001,4001,6001,548102019-112023-042026-08
Major 0Minor 15Patch 4

Each point covers 7 days.

OpenSSF Scorecard 6.4 / 10
6.4aggregate

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-22 09:58 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
1CI-Tests4 out of 30 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 13 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Gogithub.com/stretchr/testifyv1.8.1exp/go.mod
Gogo.uber.org/zapv1.26.0exp/go.mod
Gogithub.com/stretchr/testifyv1.8.1go.mod
Gogo.uber.org/goleakv1.3.0go.mod
Gogo.uber.org/multierrv1.10.0go.mod
Gogo.yaml.in/yaml/v3v3.0.4go.mod
Gogolang.org/x/vulnv1.1.4tools/go.mod
All dependencies 44

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

RegistryPackageVersionRelation
Gogithub.com/stretchr/testify1.7.0direct
Gogithub.com/stretchr/testifyv1.8.1direct
Gogo.uber.org/goleakv1.3.0direct
Gogo.uber.org/multierr1.6.0direct
Gogo.uber.org/multierrv1.10.0direct
Gogo.uber.org/multierrv1.11.0direct
Gogo.uber.org/zap0.0.0-00010101000000-000000000000direct
Gogo.yaml.in/yaml/v3v3.0.4direct
Gogolang.org/x/vuln1.1.4direct
Gogithub.com/apex/log1.1.1indirect
Gogithub.com/apex/logv1.9.0indirect
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/go-kit/kit0.9.0indirect
Gogithub.com/go-kit/logv0.2.1indirect
Gogithub.com/go-logfmt/logfmtv0.6.0indirect
Gogithub.com/go-stack/stack1.8.0indirect
Gogithub.com/go-stack/stackv1.8.1indirect
Gogithub.com/kr/prettyv0.3.0indirect
Gogithub.com/kr/textv0.2.0indirect
Gogithub.com/mattn/go-colorablev0.1.13indirect
Gogithub.com/mattn/go-isattyv0.0.19indirect
Gogithub.com/pkg/errorsv0.9.1indirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogithub.com/rogpeppe/go-internalv1.8.0indirect
Gogithub.com/rs/zerolog1.16.0indirect
Gogithub.com/rs/zerologv1.30.0indirect
Gogithub.com/sirupsen/logrus1.4.2indirect
Gogithub.com/sirupsen/logrusv1.9.3indirect
Gogolang.org/x/lint0.0.0-20190930215403-16217165b5deindirect
Gogolang.org/x/mod0.22.0indirect
Gogolang.org/x/sync0.10.0indirect
Gogolang.org/x/sys0.29.0indirect
Gogolang.org/x/sysv0.12.0indirect
Gogolang.org/x/telemetry0.0.0-20240522233618-39ace7a40ae7indirect
Gogolang.org/x/termv0.12.0indirect
Gogolang.org/x/tools0.0.0-20191029190741-b9c20aec41a5indirect
Gogolang.org/x/tools0.29.0indirect
Gogoogle.golang.org/grpc1.35.0indirect
Gogoogle.golang.org/grpcv1.56.3indirect
Gogopkg.in/check.v1v1.0.0-20201130134442-10cb98267c6cindirect
Gogopkg.in/inconshreveable/log15.v22.0.0-20180818164646-67afb5ed74ecindirect
Gogopkg.in/inconshreveable/log15.v2v2.16.0indirect
Gogopkg.in/yaml.v3v3.0.1indirect
Gohonnef.co/go/tools0.0.1-2019.2.3indirect
Dependency advisories 6

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

PackageVersionRelationSeverityAdvisoriesFixed in
google.golang.org/grpc1.35.0indirectcritical61.82.1
google.golang.org/grpcv1.56.3indirectcritical41.82.1
github.com/sirupsen/logrus1.4.2indirecthigh21.9.3
golang.org/x/mod0.22.0indirectunknown21.27.0-rc.3
golang.org/x/sys0.29.0indirectunknown10.44.0
golang.org/x/sysv0.12.0indirectunknown10.44.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.