go.uber.org/zap
Go Modulesvv1.28.0Go module: go.uber.org/zap
Not recommended for new projects
No — go.uber.org/zap should not be adopted for new projects. Depended on by 28 known packages. No license declared — you have no explicit right to use this code.
- CAdoption: grade C, Fair — worth a look.
Depended on by 28 known packages.
- BMaintenance: grade B, Good.
Last published 135 days ago. 2 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 14 transitive packages (at least — some of the tree is still being crawled).
- BSupply chain: grade B, Good.
This package lists no maintainer.
- FLicense: grade F, Failing.
No license declared — you have no explicit right to use this code.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding go.uber.org/zap to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Longest resolved dependency chain below this package.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Compatibility
- Go
- No constraint declared
Dependencies
Declared by go.uber.org/zap vv1.28.0. Runtime dependencies are installed with the package; dev dependencies are not.
Used by
Popular packages that depend on go.uber.org/zap.
Go module: github.com/minio/minio-go/v7
Go module: dev.gaijin.team/go/golib
Go module: github.com/daixiang0/gci
Go module: github.com/golangci/golangci-lint/v2
Go module: github.com/google/certificate-transparency-go
Go module: github.com/google/trillian
Go module: go.etcd.io/etcd/client/v3
Go module: go.etcd.io/etcd/etcdctl/v3
Go module: github.com/grpc-ecosystem/go-grpc-middleware
Go module: go.etcd.io/etcd/client/pkg/v3
Go module: go.etcd.io/etcd/etcdutl/v3
Go module: go.etcd.io/etcd/pkg/v3
Go module: go.etcd.io/etcd/server/v3
Go module: go.etcd.io/etcd/tests/v3
Go module: github.com/jackc/pgx/v4
Go module: github.com/GoogleCloudPlatform/cloudsql-proxy
Go module: go.etcd.io/etcd/cache/v3
Go module: gocloud.dev
Go module: github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatocumulativeprocessor
Go module: go.opentelemetry.io/collector/component
Go module: go.opentelemetry.io/collector/processor
Go module: go.opentelemetry.io/collector/internal/componentalias
Go module: go.opentelemetry.io/collector/confmap
Go module: go.opentelemetry.io/collector/confmap/xconfmap
Relationship graph
Dependencies (left) and dependents (right) of go.uber.org/zap.
Frequently installed together
Go module: go.uber.org/multierr
Go module: github.com/stretchr/testify
Go module: "gopkg.in/yaml.v3"
Go module: github.com/davecgh/go-spew
Go module: github.com/pmezard/go-difflib
Go module: golang.org/x/sys
Go module: github.com/cespare/xxhash/v2
Go module: golang.org/x/text
Go module: google.golang.org/protobuf
Go module: golang.org/x/net
Go module: github.com/coreos/go-systemd/v22
Go module: google.golang.org/grpc
Release history
2 releases in the last two years, typically about 98 days apart.
| Version | Published | License |
|---|---|---|
| v1.28.0latest | 4 months ago | — |
| v1.27.1 | 9 months ago | — |
| v1.27.0 | 2 years ago | — |
| v1.26.0 | 3 years ago | — |
| v1.25.0 | 3 years ago | — |
| v1.24.0 | 3 years ago | — |
| v1.23.0 | 4 years ago | — |
| v1.22.0 | 4 years ago | — |
| v1.21.0 | 4 years ago | — |
| v1.20.0 | 4 years ago | — |
| v1.19.1 | 5 years ago | — |
| v1.19.0 | 5 years ago | — |
| v1.18.1 | 5 years ago | — |
| v1.18.0 | 5 years ago | — |
| v1.17.0 | 5 years ago | — |
Overview
go.uber.org/zap is an Go Modules package that go module: go.uber.org/zap. It has 28 known dependents in the graph. The latest version is v1.28.0.
Who should use it
Teams working in the Go Modules ecosystem who need go module: go.uber.org/zap and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your Go Modules stack.
Pros
- Actively published to the registry.
Cons
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use go.uber.org/zap?
No — go.uber.org/zap should not be adopted for new projects. Depended on by 28 known packages. No license declared — you have no explicit right to use this code.
How do I install go.uber.org/zap?
Run `go get go.uber.org/zap` to add go.uber.org/zap to your Go Modules project.
How many dependencies does go.uber.org/zap have?
go.uber.org/zap declares 8 direct dependencies and pulls in 14 packages in total once its runtime tree is resolved.
What license is go.uber.org/zap released under?
No license was detected in go.uber.org/zap's metadata; review the repository before use.
How popular is go.uber.org/zap?
Go Modules does not publish download counts. Within PackageGraph's crawl, 28 known packages depend on go.uber.org/zap.
Is go.uber.org/zap still maintained?
The most recent release of go.uber.org/zap (vv1.28.0) was published 4 months ago.