spf13/viper

Go configuration with fangs

30.5k stars · 2.3k forks · Go

Healthy

Healthy: no known risks in the checks that ran.

Why

No rule fired.

What would change this

Maintenance

Complete

Steady

Human commits, 30 days
0
Human commits, 90 days
0
Human commits, 365 days
2
Bot share of commits, 365 days
0%
Last commit
Oct 15, 2025 (12 months ago)
Last human commit
Oct 15, 2025 (12 months ago)
Authors, 90 days
0
Last release
Sep 8, 2025 (1 year ago)
Median PR merge time
4 days

Responsiveness: of 3 recent issues, n/a got a maintainer reply. Median first response: n/a.

Sources: Commits, Releases, Merged pull requests, Issues

People

Partial
Owner
Personal account
Commits sampled
2 since Oct 14, 2025
Authors for half of commits
1
Authors for 80% of commits
2
Contributors
170

Top committers

Sources: Commits, Contributors

Stars

Complete

Organic, confidence high

Stars per week, 2014-03-30 to 2026-10-11. 3 weeks overlap a burst.Peak 140 a week2014-03-302026-10-11
Bars show stars gained each week. Orange bars overlap a burst.

Bursts

Anyone can buy stars for any repo; bursts alone don't prove the owner did.

Sources: How star history is analyzed

Risk

Complete

Flags

No risk flags.

License

Now
MIT (OSI-approved)
A year ago
MIT (OSI-approved)

Packages

Package and advisory data: deps.dev and OSV.

OpenSSF Scorecard: 4.5 out of 10 (via deps.dev).

Sources: GitHub: spf13/viper, deps.dev: Go github.com/spf13/viper

Badge

Add this to a README to show the current verdict:

[![RepoRadar](https://reporadar.ai/spf13/viper/badge.svg)](https://reporadar.ai/spf13/viper)

Earlier verdicts

Computed 11 hours ago · method 2026.10.2