github.com/spf13/viper
Go Modulesvv1.21.0Go module: github.com/spf13/viper
Not recommended for new projects
No — github.com/spf13/viper should not be adopted for new projects. Depended on by 4 known packages. Last published 366 days ago. 3 releases in the last 2 years. Pulls in 46 transitive packages (at least — some of the tree is still being crawled). No license declared — you have no explicit right to use this code.
- CAdoption: grade C, Fair — worth a look.
Depended on by 4 known packages.
- CMaintenance: grade C, Fair — worth a look.
Last published 366 days ago. 3 releases in the last 2 years.
- CWeight: grade C, Fair — worth a look.
Pulls in 46 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 github.com/spf13/viper 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 github.com/spf13/viper vv1.21.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (17)
Used by
Popular packages that depend on github.com/spf13/viper.
Go module: github.com/minio/minio-go/v7
Go module: github.com/vektra/mockery/v2
Go module: github.com/golangci/golangci-lint/v2
Go module: github.com/tomarrell/wrapcheck/v2
Relationship graph
Dependencies (left) and dependents (right) of github.com/spf13/viper.
Frequently installed together
Go module: golang.org/x/text
Go module: github.com/spf13/cast
Go module: github.com/spf13/pflag
Go module: "gopkg.in/yaml.v3"
Go module: github.com/mitchellh/mapstructure
Go module: github.com/spf13/afero
Go module: golang.org/x/sync
Go module: github.com/fsnotify/fsnotify
Go module: github.com/stretchr/testify
Go module: github.com/pelletier/go-toml/v2
Go module: golang.org/x/sys
Go module: github.com/subosito/gotenv
Release history
3 releases in the last two years, typically about 43 days apart.
| Version | Published | License |
|---|---|---|
| v1.21.0latest | 1 year ago | — |
| v1.20.1 | 1 year ago | — |
| v1.20.0 | 1 year ago | — |
| v1.20.0-alpha.6 | 2 years ago | — |
| v1.20.0-alpha.5 | 2 years ago | — |
| v1.20.0-alpha.4 | 2 years ago | — |
| v1.20.0-alpha.3 | 2 years ago | — |
| v1.20.0-alpha.2 | 2 years ago | — |
| v1.20.0-alpha.1 | 2 years ago | — |
| v1.19.0 | 2 years ago | — |
| v1.18.2 | 2 years ago | — |
| v1.18.1 | 2 years ago | — |
| v1.18.0 | 2 years ago | — |
| v1.17.0 | 2 years ago | — |
| v1.16.0 | 3 years ago | — |
Overview
github.com/spf13/viper is an Go Modules package that go module: github.com/spf13/viper. It has 4 known dependents in the graph. The latest version is v1.21.0.
Who should use it
Teams working in the Go Modules ecosystem who need go module: github.com/spf13/viper and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your Go Modules stack.
Pros
- Actively published to the registry.
Cons
- Large dependency tree (17 direct dependencies) increases install size and audit surface.
- 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 github.com/spf13/viper?
No — github.com/spf13/viper should not be adopted for new projects. Depended on by 4 known packages. Last published 366 days ago. 3 releases in the last 2 years. Pulls in 46 transitive packages (at least — some of the tree is still being crawled). No license declared — you have no explicit right to use this code.
How do I install github.com/spf13/viper?
Run `go get github.com/spf13/viper` to add github.com/spf13/viper to your Go Modules project.
How many dependencies does github.com/spf13/viper have?
github.com/spf13/viper declares 17 direct dependencies and pulls in 46 packages in total once its runtime tree is resolved.
What license is github.com/spf13/viper released under?
No license was detected in github.com/spf13/viper's metadata; review the repository before use.
How popular is github.com/spf13/viper?
Go Modules does not publish download counts. Within PackageGraph's crawl, 4 known packages depend on github.com/spf13/viper.
Is github.com/spf13/viper still maintained?
The most recent release of github.com/spf13/viper (vv1.21.0) was published 1 year ago.